[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes: > Has anyone come up with a good solution? The last one I saw from Tom > Lane required compile-time options which isn't an option for us. As far as I know it's fixed in the currently-committed sources. The key is to do case normalization for keyword-testing separately from case normalization of an identifier (after it's been determined not to be a keyword). Amazingly enough, SQL99 actually requires this... In Turkish this means that either INSERT or insert will be seen as a keyword, while either XINSERT or xinsert will become "xýnsert". regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
- [HACKERS] Re: [BUGS] Turkish locale bug Tom Lane
- Re: [HACKERS] Re: [BUGS] Turkish locale bug Larry Rosenman
- Re: [HACKERS] Re: [BUGS] Turkish locale bug Tom Lane
- Re: [HACKERS] Re: [BUGS] Turkish locale... Larry Rosenman
- [HACKERS] Re: Turkish locale bug Justin Clift
- [HACKERS] Re: Turkish locale bug Tom Lane
- [HACKERS] Re: Turkish locale bug Sezai YILMAZ
- Re: [HACKERS] Re: Turkish locale bug Trond Eivind Glomsrød
- Re: [HACKERS] Re: Turkish locale bu... Tom Lane
- Re: [HACKERS] Re: Turkish loca... Tom Lane
- [HACKERS] Re: [BUGS] Turkish locale bug Sezai YILMAZ
- [HACKERS] Re: [BUGS] Turkish locale bug Tom Lane
- [HACKERS] Re: [BUGS] Turkish locale bug Thomas Lockhart
- [HACKERS] Re: [BUGS] Turkish locale... Tom Lane
- [HACKERS] Re: [BUGS] Turkish l... Thomas Lockhart
- [HACKERS] Re: [BUGS] Turki... Tom Lane