Re: server , client encoding issue

how can i change the client encoding to LATIN1?
i know it can be done by changing the postgresql.conf

but i want to include it in the code ...

is it possible that PQconnectdb can take a parameter for client encoding if yes how??

if PQconnectdb can not handle it ..please tell as to how which is the method i can use for doing the above

________________________________

From: Richard Huxton [mailto:dev(at)archonet(dot)com]
Sent: Thu 10/20/2005 1:00 PM
To: surabhi.ahuja
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] server , client encoding issue

***********************
Your mail has been scanned by InterScan VirusWall.
***********-***********

surabhi.ahuja wrote:
> i checked the locale it is giving:
>
> LANG=en_US.iso885915
> LC_CTYPE="en_US.iso885915"

If you Google for "ISO-8859-15 Latin9" the top two results seem to give
details. Oh - there are two naming systems for character sets, just to
make things even more complicated.

Now, traditionally you'd have used Latin1 (ISO-8859-1), but the
introduction of the Euro meant they needed to introduce a new character.
They took the opportunity to make some other changes too and called the
results Latin9 (ISO-8859-15).

OK - now the original problem was with a database not having a UNICODE
encoding. It does look like this is because the environment on this
machine is Latin9 rather than UTF-8. It's easy to have this problem, and
I always recommend setting the encoding explicitly when creating a
database cluster (initdb --encoding=UTF8). If you installed from a
package, it might have chosen a default for you though.

HTH
--
Richard Huxton
Archonet Ltd