> > Did time become a keyword in 7.2? 7.1.3 allowed it as a column name...
> > 7.2 rejects it.
> 
> Yes. We now support SQL99 time and timestamp precision, which require
> that TIME(p) be a type specification. So there are parts of the grammar
> which cannot easily fit "time" anymore.

Isn't the grammar explicit enough to distinguish a value (in this case function 
call) from a type name ? It seems a type name will only appear in very specific 
contexts.
Imho it would be nice if we could allow "select timestamp(xxx);",
and this has been the umpteenth request in this regard, and 7.2 is not even 
released yet.

Andreas

Wed, 9 Jan 2002 09:45:09 +0100
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: Time as keyword
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> Imho it would be nice if we could allow "select timestamp(xxx);",
> and this has been the umpteenth request in this regard, and 7.2 is not even 
> released yet.

Unfortunately, there's just no way.  If we tried, it would be ambiguous
whether, say, "timestamp(6)" is a function call or a type name.

This is not one of my favorite parts of SQL92 syntax :-(

			regards, tom lane

Wed, 09 Jan 2002 10:28:24 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: Time as keyword 
...
> Imho it would be nice if we could allow "select timestamp(xxx);",
> and this has been the umpteenth request in this regard, and 7.2 is not even
> released yet.

afaicr one of the very sticky areas is the SQL99-specified syntax for
date/time literals:

  timestamp(6) '2001-01-08 04:05:06'

which is difficult to reconcile with a function named timestamp:

  timstamp(something)

                       - Thomas

Wed, 09 Jan 2002 16:24:40 +0000
Thomas Lockhart <lockhart@fourpalms.org>
Re: Time as keyword