| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
| Cc: | Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr>, Justin Clift <aa2(at)bigpond(dot)net(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Turkish locale bug |
| Date: | 2001-03-03 00:11:00 |
| Message-ID: | 4933.983578260@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
teg(at)redhat(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-03 00:13:29 | Re: Re: Turkish locale bug |
| Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-03-02 23:46:10 | Re: Re: Turkish locale bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-03 00:13:29 | Re: Re: Turkish locale bug |
| Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-03-02 23:46:10 | Re: Re: Turkish locale bug |