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

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

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: "John Hansen" <john(at)geeknet(dot)com(dot)au>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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 00:45:54
Message-ID: 5066E5A966339E42AA04BA10BA706AE5625B@rodrick.geeknet.com.au (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
> currently, upper/lower does not work with 2+ byte unicode 
> characters, on any OS under the C locale.

Btw,...

There are only 15 cases in the utf8 repertoire that depends on locale, these are the only cases where pg should report:

ERROR:  invalid multibyte character for locale
HINT:  The server's LC_CTYPE locale is probably incompatible with the database encoding.

When doing a select upper/lower (col)
All others should work just fine.

The error should probably also be changed to a warning, and just return the offending character unmodified.


... John

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-02-25 01:11:43
Subject: Re: Finding if old transactions are running...
Previous:From: John HansenDate: 2005-02-25 00:29:32
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

pgsql-hackers-win32 by date

Next:From: Bruce MomjianDate: 2005-02-25 03:05:57
Subject: Re: [pgsql-hackers-win32] Repleacement for src/port/snprintf.c
Previous:From: John HansenDate: 2005-02-25 00:29:32
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

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