Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Hansen" <john(at)geeknet(dot)com(dot)au>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>,"Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"Magnus Hagander" <mha(at)sollentuna(dot)net>,"Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>,pgsql-hackers-win32(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Date: 2005-02-25 19:17:42
Message-ID: 7304.1109359062@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
> Right, so for the sample SQL I sent earlier, the result would be the same as the input?
> That's hardly a working upper/lower....

[ shrug... ]  It works per the locale definition, which is that only
7-bit-ASCII a-z/A-Z get converted.

The bottom line here is that we rely on the locale setting for this
behavior, and that's not likely to change real soon.  If you dislike
the locale definition then you should be using a different locale.
In particular I think the issue here is really that your platform's
definition of "C locale" says that bytes above x7F are illegal
characters.  My platform's doesn't.  The thing to be changing is the
locale definition.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: yo meroDate: 2005-02-25 19:29:54
Subject: CAN-2005-0247
Previous:From: John HansenDate: 2005-02-25 18:38:29
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

pgsql-hackers-win32 by date

Next:From: Bruce MomjianDate: 2005-02-27 00:54:00
Subject: Re: win32 performance - fsync question
Previous:From: John HansenDate: 2005-02-25 18:38:29
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group