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 15:18:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-hackers-win32
"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
>> Sure it does.  It's just that the defined behavior of the C 
>> locale is often useless in practice.

> select upper('');
> ERROR:  invalid multibyte character for locale
> HINT:  The server's LC_CTYPE locale is probably incompatible with the database encoding.

> Consequently it seems that is does not work.

"It fails on my machine" should not be read as "it doesn't work for anyone".
It all depends on how your local mbstowcs() works.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-02-25 15:23:16
Subject: Re: Where are we on stored procedures?
Previous:From: Tom LaneDate: 2005-02-25 15:13:23
Subject: Re: Where are we on stored procedures?

pgsql-hackers-win32 by date

Next:From: John HansenDate: 2005-02-25 18:17:48
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Previous:From: Nicolai TufarDate: 2005-02-25 11:08:10
Subject: Re: [pgsql-hackers-win32] Repleacement for src/port/snprintf.c

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