Re: [PATCHES] Non-colliding auto generated names - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Non-colliding auto generated names
Date
Msg-id 3096.1046916539@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Non-colliding auto generated names  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: [PATCHES] Non-colliding auto generated names  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
>> I think we should stick with the existing naming convention.
^^^^^^^^^^^^^^^^^^^^^^^^^^

> Non-colliding?

No; see above.

> Otherwise, it'd be ludicrous to fail a table rename because
> a sequence with the new name already exists...

Why?  We already rename the table's rowtype, ergo you can fail a table
rename because there is a conflicting datatype name.  I don't see
anything much wrong with failing a table or column rename because there
is a conflicting sequence name.  The whole point here is to have a
non-surprising mapping between the names of serial columns and the names
of their associated sequences.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: [PATCHES] Non-colliding auto generated names
Next
From: cbbrowne@cbbrowne.com
Date:
Subject: Re: XML ouput for psql