Re: Re: Turkish locale bug

Trond Eivind Glomsrød <teg@redhat.com>

From: teg@redhat.com (Trond Eivind Glomsrød )
To: Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr>
Cc: Justin Clift <aa2@bigpond.net.au>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2001-03-02T23:46:10Z
Lists: pgsql-bugs, pgsql-hackers

Attachments

Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr> writes:

> Justin Clift wrote:
> > 
> > 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.
> 
> 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.