It would appear the spec was approved of before we got foo.nextval, so
here it is again.
NEXT VALUE FOR and CURRENT VALUE FOR where CURRENT is an unreserved
keyword and VALUE is not reserved in any way (ident with comparison to
This allows the default of a table to depend on a sequence, CASCADE drop
of the sequence removes removes references to it.
CURRENT VALUE FOR is an extension of the spec.
This gives us almost everything required for the Sequence feature (T176)
(as per the draft).
We're missing the datatype specification on the sequence.
CREATE SEQUENCE t AS numeric(130);
Rod Taylor <rbt ( at ) rbt ( dot ) ca> writes:
> Are you ok with the DB2 and draft-spec syntax of NEXT VALUE FOR (where
> value is not a reserved word)? Or should I hold onto that until the
> spec has gone through the final draft / release?
By that time we'll have done the Oracle-style foo.nextval, and it'll
become kind of a moot point ;-)
regards, tom lane
pgsql-patches by date
|Next:||From: Bruce Momjian||Date: 2004-04-21 00:34:53|
|Subject: Change of CSV keywords|
|Previous:||From: Michiel Ephraim||Date: 2004-04-20 21:57:14|
|Subject: Re: build annoyences|