Re: Turkish locale bug
Justin Clift <aa2@bigpond.net.au>
From: Justin Clift <aa2@bigpond.net.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr>, pgsql-bugs@postgresql.org, pgsql-hackers@postgresql.org
Date: 2001-02-20T03:30:26Z
Lists: pgsql-bugs, pgsql-hackers
Tom Lane wrote: > > Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr> writes: > > With Turkish locale it is not possible to write SQL queries in > > CAPITAL letters. SQL identifiers like "INSERT" and "UNION" first > > are downgraded to "ýnsert" and Then "ýnsert" and "unýon" > > does not match as SQL identifier. > > Ugh. <snip> How about thinking in the other direction.... is it possible for PostgreSQL to be able to recognised localised versions of SQL queries? i.e. For a Turkish locale it associates "ýnsert" INSERT and "unýon" with UNION. Perhaps including this in the compilation stage (checking which locates are installed on a system, or maybe which locales are specified somewhere)? Not sure what this would do to performance though, as having to do extra SQL identifier matching might be a bit slow. This would have the advantage of the present SQL queries out there working. Regards and best wishes, Justin Clift Database Administrator