On Tue, 2003-05-27 at 00:21, Tom Lane wrote:
> Rod Taylor <rbt@rbt.ca> writes:
> > I don't see PREVIOUS as a reserved word, but CURRENT
> > certainly is -- WHERE CURRENT OF for cursors, and several other places.
>
> > The attached patch makes CURRENT a reserved word.
>
> I do not think it will be necessary to treat CURRENT as a fully-reserved
> word in order to support WHERE CURRENT OF, and accordingly I'm not very
Very well.. I'll hold onto the CURRENT portion until the term current
has been reserved (bound to happen eventually if we implement all of
SQL99).
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?
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
