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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: [HACKERS] 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: [HACKERS] UNICODE/UTF-8 on win32
  • Date: Fri, 25 Feb 2005 10:18:35 -0500
  • Message-id: <5100(dot)1109344715(at)sss(dot)pgh(dot)pa(dot)us>

"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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group