Mailing List Archive

I Have done that many times without issues .

On Tue, Jul 7, 2020, 2:16 PM Rue, Randy <randyrue@gmail.com> wrote:

> We're changing our layouts and it would make functional sense to have a
> consistent naming scheme include an existing aggregate.
>
> Is there any impact from renaming an aggregate other than a new display
> name?
>
> Randy
>
> _______________________________________________
> Toasters mailing list
> Toasters@teaparty.net
> https://www.teaparty.net/mailman/listinfo/toasters
>

None whatsoever. The only aggregate you can’t rename are Snaplock
aggregates.


On July 7, 2020 at 14:16:40, Randy Rue, (randyrue@gmail.com) wrote:

We're changing our layouts and it would make functional sense to have a
consistent naming scheme include an existing aggregate.

Is there any impact from renaming an aggregate other than a new display
name?

Randy

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
https://www.teaparty.net/mailman/listinfo/toasters

Cool. On it. Thanks!

On 7/7/2020 4:05 PM, André M. Clark wrote:
> None whatsoever. The only aggregate you can’t rename are Snaplock
> aggregates.
>
>
> On July 7, 2020 at 14:16:40, Randy Rue, (randyrue@gmail.com
> <mailto:randyrue@gmail.com>) wrote:
>
>> We're changing our layouts and it would make functional sense to have a
>> consistent naming scheme include an existing aggregate.
>>
>> Is there any impact from renaming an aggregate other than a new display
>> name?
>>
>> Randy
>>
>> _______________________________________________
>> Toasters mailing list
>> Toasters@teaparty.net <mailto:Toasters@teaparty.net>
>> https://www.teaparty.net/mailman/listinfo/toasters