| From: | Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr> |
|---|---|
| To: | Justin Clift <aa2(at)bigpond(dot)net(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 08:44:55 |
| Message-ID: | 3A922E87.D98375E7@ata.cs.hun.edu.tr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Justin Clift wrote:
>
> 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.
I don't have any opinion how can solve this problem. But,
I don't agree with this solution. SQL is naturally English. I am
against SQL to be localized.
regards
-sezai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sezai YILMAZ | 2001-02-20 09:00:02 | Re: Re: Turkish locale bug |
| Previous Message | Tom Lane | 2001-02-20 03:37:52 | Re: Turkish locale bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sezai YILMAZ | 2001-02-20 09:00:02 | Re: Re: Turkish locale bug |
| Previous Message | Justin Clift | 2001-02-20 08:44:40 | Re: beta5 ... |