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

Re: Re: Turkish locale bug

From: teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
To: Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr>
Cc: Justin Clift <aa2(at)bigpond(dot)net(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Turkish locale bug
Date: 2001-03-02 23:46:10
Message-ID: xuy7l274tvh.fsf@halden.devel.redhat.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr> writes:

> 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.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-03 00:11:00
Subject: Re: Re: Turkish locale bug
Previous:From: Martin A. MarquesDate: 2001-03-02 22:10:46
Subject: Re: PostgreSQL for Solaris packages

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-03-03 00:11:00
Subject: Re: Re: Turkish locale bug
Previous:From: pgsql-bugsDate: 2001-03-02 23:24:22
Subject: polygon insert into r-tree sometimes fails

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