On Wed, Aug 17, 2016 at 3:52 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes:
>> Here is a patch for implementing the NEXT VALUE FOR expression.  This is
>> the SQL-standard conforming version of our nextval() function, and it's
>> also used by Oracle, MS SQL, DB2.  Example:
> We discussed this before and concluded that NEXT VALUE FOR is in fact
> *not* an exact semantic equivalent of nextval():
> https://www.postgresql.org/message-id/14790.1083955136%40sss.pgh.pa.us

And also again 10 years later when I proposed it :-)


> I remain of the opinion that using spec-compliant syntax for
> non-spec-compliant behavior isn't a great advance.

Thomas Munro

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to