Re: Re: Turkish locale bug
От | teg@redhat.com (Trond Eivind Glomsrød) |
---|---|
Тема | Re: Re: Turkish locale bug |
Дата | |
Msg-id | xuy7l274tvh.fsf@halden.devel.redhat.com обсуждение исходный текст |
Ответ на | Re: Turkish locale bug (Sezai YILMAZ <sezaiy@ata.cs.hun.edu.tr>) |
Ответы |
Re: Re: Turkish locale bug
|
Список | pgsql-hackers |
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. Has anyone come up with a good solution? The last one I saw from Tom Lane required compile-time options which isn't an option for us. -- Trond Eivind Glomsrød Red Hat, Inc.
В списке pgsql-hackers по дате отправления: