Skip site navigation (1) Skip section navigation (2)

Re: Turkish locale bug

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Sezai YILMAZDate: 2001-02-20 09:00:02
Subject: Re: Re: Turkish locale bug
Previous:From: Justin CliftDate: 2001-02-20 08:44:40
Subject: Re: beta5 ...

pgsql-bugs by date

Next:From: Sezai YILMAZDate: 2001-02-20 09:00:02
Subject: Re: Re: Turkish locale bug
Previous:From: Tom LaneDate: 2001-02-20 03:37:52
Subject: Re: Turkish locale bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group