From: | Tim Allen <tim(at)proximity(dot)com(dot)au> |
---|---|
To: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: new FAQ entry |
Date: | 2006-06-08 07:19:26 |
Message-ID: | 4487CF7E.9060909@proximity.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tino Wildenhain wrote:
> Tim Allen schrieb:
[snip]
>> The way to tell PostgreSQL what encoding you want to use is by use of
>> the client_encoding GUC variable, eg
>>
>> set client_encoding to 'LATIN1';
>
>
> If you cant educate your client application to set this option on connect,
> you can set this per user:
>
> ALTER USER clientappuser SET client_encoding to 'what your app uses';
Good point. I guess it's worth mentioning this and some of the other
ways you can set the encoding. Though there are actually quite a few
different ways - that might make the entry overly long. Opinions?
Tim
--
-----------------------------------------------
Tim Allen tim(at)proximity(dot)com(dot)au
Proximity Pty Ltd http://www.proximity.com.au/
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2006-06-08 09:05:02 | Re: UTF8 problem |
Previous Message | Tino Wildenhain | 2006-06-08 07:10:48 | Re: new FAQ entry |