So is it to make SQL parser context-sensitive - say the parser will understand that in statement "SELECT * from LIMIT", LIMIT is just a table name, instead of keyword?
There might be some conflicts when using Yacc, but I am not sure how difficult will be ... Cheers, Qingqing "Christopher Kings-Lynne" <[EMAIL PROTECTED]> > You will still need to use double quotes in 8.0.1... > > Chris > > Gourish Singbal wrote: > > Thanks a lot, > > > > we might be upgrading to 8.0.1 soon.. till than using double quotes > > should be fine. > > > > regards > > gourish > > > > On Mon, 14 Mar 2005 18:25:22 +1100, Russell Smith <[EMAIL PROTECTED]> wrote: > > > >>On Mon, 14 Mar 2005 06:14 pm, Gourish Singbal wrote: > >> > >>>Guys, > >>> > >>>I am having a problem firing queries on one of the tables which is > >>>having "limit" as the column name. > >>> > >>>If a run an insert/select/update command on that table i get the below error. > >>> > >>>ERROR: syntax error at or near "limit" at character 71 > >> > >>select "limit" from limit_table WHERE "limit" < 50 LIMIT 2; > >> > >>You need to quote the field name, and make sure the case is correct. > >> > >>>Any Help would be realyl great to solve the problem. > >>> > >>>postgresql 7.4.5 and linux OS > >>> > >> > >>You should probably upgrade to 7.4.7 > >> > >>Regards > >> > >>Russell Smith. > >> > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) > ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])