RE: create table bug with reserved words?

Peter Eisentraut wrote:

>But since the problematic word in your case is not CALL but SELECT, I can
>tell you right away with relative certainty that it will not be possible
>to change the parser to accept SELECT as an identifier in all contexts
>without butchering the grammar beyond reason.

Just found out how MSSQL does it...it cheats!
The parser takes 'create table test (select int)' and converts it into
'create table test ([select] int)'.
I guess that this isn't an SQL92/99 compliant method :)

Thanks for the help,
Chris