From: | Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Justin Clift <aa2(at)bigpond(dot)net(dot)au>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Re: Turkish locale bug |
Date: | 2001-02-20 09:00:02 |
Message-ID: | 3A923212.848AAEA2@ata.cs.hun.edu.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
>
> Justin Clift <aa2(at)bigpond(dot)net(dot)au> writes:
> > 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.
>
> Hmm. Wouldn't that mean that if someone actually wrote ınsert,
> it would be taken as matching the INSERT keyword, not as an identifier?
> If I understood Sezai correctly, that would surprise a Turkish user.
> But if this behavior is OK then you might have a good answer.
This solution is simple and clear. But it is not a good solution,
I think. I don't prefer "ınsert" to be understood as "INSERT" and
"unıon" as "UNION" in SQL keywords. I think this behaviour is not
OK.
It should be better to write functions isalpha_en(), isupper_en()
and tolower_en() which actually behave with English locale. Then
use these function in that block.
regards
-sezai
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sezai YILMAZ | 2001-02-20 09:24:59 | Re: Turkish locale bug |
Previous Message | Sezai YILMAZ | 2001-02-20 08:44:55 | Re: Turkish locale bug |
From | Date | Subject | |
---|---|---|---|
Next Message | Sezai YILMAZ | 2001-02-20 09:24:59 | Re: Turkish locale bug |
Previous Message | Sezai YILMAZ | 2001-02-20 08:44:55 | Re: Turkish locale bug |