-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Mon, 15 Dec 2003, Tom Lane wrote:
> > As you can see "I" in "VOID" gets converted to i-dotless in conformance
> > to tr_TR Locale conversion rules, which is not an expected behaviour for
> > Turkish users who set their locale to tr_TR.
>
> Why is it not expected behavior? The SQL99 spec has not changed from
> what it said when we discussed this last year: case conversion of
> identifiers is *not* to be done in plain-ASCII rules. Admittedly it
> says "unicode" and not "locale", but you'd have the same problem if we
> had a full unicode implementation, no?
I'm pretty sure that Nicolai will explain things better; so it's better to
wait for his e-mail.
If PostgreSQL had a full unicode implementation, as you've said: Yes, we
would experience the same problems.
We also have a problem while sorting result in a SELECT query, which seems
a similar issue as this one. In Turkish, i-dotless comes just before i in
alphabet; but PostgreSQL places i-dotless 'after' i, which is a false
result. Nicolai will also report this bug, and explain why/how it happens.
> My feeling is that the best answer is to use lower case names to
> reference identifiers in the initdb code. This is not a real pleasant
> prospect, but I can't see giving up on spec-compatible case folding ...
This is what we've also thought in here.
Regards,
- --
Devrim GUNDUZ
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE/3iwVtl86P3SPfQ4RAl1VAJ9vmbEwq2pbAoPWY+lmVKSLhhabJQCgrzN9
zIRLFXS5WxjnZKbaO9XviA4=
=SDYx
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
