Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Non-colliding auto generated names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rod Taylor <rbt(at)rbt(dot)ca>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Non-colliding auto generated names
Date: 2003-03-05 21:53:20
Message-ID: 27910.1046901200@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Rod Taylor <rbt(at)rbt(dot)ca> writes:
> 200N spec proposes 'NEXT VALUE FOR <sequence>'.
> Tom will shoot me if I submit that though (VALUE as a keyword again).  I
> suppose one could make it a variable, and confirm it's value is VALUE?

> Anyway, once again we could extend to include:
> NEXT VALUE ON table(column)?

This is looking messier and messier.  And, you are all conveniently
ignoring the fact that any change in sequence naming conventions will
break existing applications.  Offering some completely new syntax
that they're supposed to use instead won't make people any happier.

I think we should stick with the existing naming convention.  The only
actual problem that's been pointed out here is that an ALTER TABLE
(or COLUMN) RENAME on a serial column doesn't update the sequence name
to match.  Seems to me we could fix that with less effort than any of
these solutions would take, and it wouldn't break existing applications.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2003-03-05 22:37:35
Subject: Re: XML ouput for psql
Previous:From: Bruce MomjianDate: 2003-03-05 21:52:44
Subject: Re: request for sql3 compliance for the update command

pgsql-patches by date

Next:From: Peter EisentrautDate: 2003-03-05 22:37:35
Subject: Re: XML ouput for psql
Previous:From: Bruce MomjianDate: 2003-03-05 20:04:04
Subject: Re: [PATCHES] Non-colliding auto generated names

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group