Re: Unicode problem ??? - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: Unicode problem ???
Date
Msg-id 20040421215725.Q817@hermes.hilbert.loc
Whole thread Raw
In response to Re: Unicode problem ???  ("Stijn Vanroye" <s.vanroye@farcourier.com>)
List pgsql-general
> What I personally don't understand is: if all my databases
> are UNICODE, why do I have to set the Client encoding to latin1
> to get a correct result?
Because LATIN1 isn't just a subset of UNICODE. If the data
coming out of the database *is* UNICODE *and* your client
*does* handle UNICODE directly you might get away with not
setting a client_encoding, same goes for DB=latin1 +
client=latin1. If, however, the DB delivers UNICODE but your
client really wants LATIN1 you need to tell the database to
convert the stored UNICODE to LATIN1 before delivery. That's
what the client_encoding is for.

Or so is my understanding of it.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

pgsql-general by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly over time
Next
From: "scott.marlowe"
Date:
Subject: Re: kill -2