Christopher Kings-Lynne [EMAIL PROTECTED] writes:
I actually like the NEXT VALUE FOR a lot more. The reason is that the
Oracle syntax is very much an 'object.property' lookup, which we do nowhere
else in PostgreSQL.
I beg to differ. We have supported table.function since day one ---
it's in
(Moved to -hackers)
Rod Taylor [EMAIL PROTECTED] 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
