Re: Re: Turkish locale bug
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: teg@redhat.com (Trond Eivind Glomsrød )
Cc: Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr>,
Justin Clift <aa2@bigpond.net.au>, pgsql-hackers@postgresql.org
Date: 2001-03-03T00:11:00Z
Lists: pgsql-bugs, pgsql-hackers
teg@redhat.com (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 "xnsert". regards, tom lane