Tom Lane wrote: > If the parser treated PUBLIC as an actual keyword, you'd not be having > this problem, because keywords are case-folded on an ASCII-only basis > (which is consistent with the SQL99 spec, amazingly enough). > > We put in the above hack after someone complained that PUBLIC didn't use > to be a reserved word ... but considering that SQL92 clearly lists it as > a reserved word, there's not a lot of ground for that complaint to stand > on. > > I'd prefer shifting PUBLIC back to the true-keyword category over any > of the other workarounds you've suggested ...
PUBLIC doesn't seem like a very common column name --- seems safe to make it reserved. We made 'value' reserved in 7.3, and that was a much more common one. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
