Re: NEXT VALUE FOR - Mailing list pgsql-hackers

From Tom Lane
Subject Re: NEXT VALUE FOR
Date
Msg-id 25659.1412257681@sss.pgh.pa.us
Whole thread Raw
In response to NEXT VALUE FOR  (Thomas Munro <munro@ip9.org>)
Responses Re: NEXT VALUE FOR
List pgsql-hackers
Thomas Munro <munro@ip9.org> writes:
> SQL:2003 introduced the function NEXT VALUE FOR <sequence>. Google
> tells me that at least DB2, SQL Server and a few niche databases
> understand it so far.  As far as I can tell there is no standardised
> equivalent of currval and setval (but I only have access to second
> hand information about the standard, like articles and the manuals of
> other products).

Have you checked the archives about this?  My recollection is that one
reason it's not in there (aside from having to reserve "NEXT") is that
the standard-mandated semantics are not the same as nextval().
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bogdan Pilch
Date:
Subject: Re: Time measurement format - more human readable
Next
From: Alvaro Herrera
Date:
Subject: Re: Per table autovacuum vacuum cost limit behaviour strange