Re: Locale-based identifier conversion and Turkish - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Locale-based identifier conversion and Turkish
Date
Msg-id 14537.1071519263@sss.pgh.pa.us
Whole thread Raw
In response to Locale-based identifier conversion and Turkish  (Devrim GUNDUZ <devrim@gunduz.org>)
Responses conversion_create.sql  (Michael Brusser <michael@synchronicity.com>)
Re: Locale-based identifier conversion and Turkish  (Devrim GUNDUZ <devrim@gunduz.org>)
List pgsql-hackers
Devrim GUNDUZ <devrim@gunduz.org> writes:
> Now, PostgreSQL 7.4 initdb fails if run with locale set to tr_TR:

Ugh :-(

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

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 ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] fork/exec patch
Next
From: Michael Brusser
Date:
Subject: conversion_create.sql