I said:
> In Turkish this means that either INSERT or insert will be seen as
> a keyword, while either XINSERT or xinsert will become "xýnsert".
Sheesh. Gotta think twice before pressing SEND. That should be
INSERT -> keyword
insert -> keyword
XINSERT -> "xýnsert"
[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> 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.
As far as I know it's fixed in the currently-committed sources. The
key is to do case nor
Sezai YILMAZ <[EMAIL PROTECTED]> writes:
> Justin Clift wrote:
> >
> > Tom Lane wrote:
> > >
> > > Sezai YILMAZ <[EMAIL PROTECTED]> writes:
> > > > With Turkish locale it is not possible to write SQL queries in
> > > > CAPITAL letters. SQL identifiers like "INSERT" and "UNION" first
> > > > are
Justin Clift wrote:
>
> Tom Lane wrote:
> >
> > Sezai YILMAZ <[EMAIL PROTECTED]> 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"
>
Justin Clift <[EMAIL PROTECTED]> writes:
> 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.
Hmm. Wouldn't that mean that
Tom Lane wrote:
>
> Sezai YILMAZ <[EMAIL PROTECTED]> 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.
