Re: Turkish locale bug

From: Justin Clift <aa2(at)bigpond(dot)net(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Turkish locale bug
Date: 2001-02-20 03:30:26
Message-ID: 3A91E4D2.4C013AB7@bigpond.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Tom Lane wrote:
>
> Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-02-20 03:37:52 Re: Turkish locale bug
Previous Message Larry Rosenman 2001-02-20 03:15:23 Re: [HACKERS] Re: Turkish locale bug

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-20 03:37:52 Re: Turkish locale bug
Previous Message Larry Rosenman 2001-02-20 03:15:23 Re: [HACKERS] Re: Turkish locale bug