From: | Marko Karppinen <marko(at)karppinen(dot)fi> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Subject: | Re: Rough draft for Unicode-aware UPPER()/LOWER()/INITCAP() |
Date: | 2004-05-17 07:13:54 |
Message-ID: | C1763111-A7D1-11D8-9207-000A95C56374@karppinen.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
>> initdb could even emit a warning if the --encoding option was
>> used without also specifying --no-locale.
>
> Please don't do that. Most Asian chasets does not work with locale
> enabled PostgreSQL installation. i.e. it returns WRONG SELECT
> results. I've been telling this to Japanese users for hundreds of
> times when they ask me why SELECT returns results. If that kind of
> wanings are installed, I think more Japanese users will be confused.
You've advocated a default of --no-locale yourself for this reason.
If using a Japanese --encoding setting without --no-locale emitted
a warning suggesting the use of --no-locale, I'd imagine you wouldn't
have had to give human support to most of those hundreds of people?
Wouldn't that be a halfway point to your goal?
mk
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Karppinen | 2004-05-17 07:29:26 | Re: enabling tcpip_socket by default |
Previous Message | Hans-Jürgen Schönig | 2004-05-17 07:11:20 | Re: Call for 7.5 feature completion |