Re: new FAQ entry

From: Erik Jones <erik(at)myemma(dot)com>
To: Tim Allen <tim(at)proximity(dot)com(dot)au>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: new FAQ entry
Date: 2006-06-08 14:17:10
Message-ID: 44883166.6020705@myemma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tim Allen wrote:
> 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

You could always go with one solution in the faq, such as the one you've
already given, and list and link to others near the end. In fact, this
is probably best without at least mentioning the other solutions newbies
(like me) might never look furthur to find, what for them, might be a
better, or more fitting, solution...

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jqpx37 2006-06-08 15:08:32 Re: Password for postgresql superuser?
Previous Message Daniel Verite 2006-06-08 14:08:26 Re: UTF8 problem