| From: | Chris Storah <cstorah(at)emis-support(dot)demon(dot)co(dot)uk> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | RE: create table bug with reserved words? |
| Date: | 2001-02-16 17:16:56 |
| Message-ID: | C05E7DA1218ED411BF8A00105AC95A8E016F8CE2@SV-CNTRMAIL |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-02-16 19:59:00 | Re: On NetBSD, had to add -Wl,-R/usr/local/postgres/lib to the src/Makefile.global LIB variable |
| Previous Message | Tom Lane | 2001-02-16 17:11:34 | Re: create table bug with reserved words? |