Re: pgadmin3 clientencoding

Jean-Michel POURE wrote:

>On Tuesday 10 June 2003 11:11, you wrote:
>
>
>>>Do we really need special encodings, besides unicode? If so, this
>>>should be implemented on a tree node (Server property: client
>>>encoding) to make it possible to let the change of encoding have
>>>immediate effect, or as the "System Object" setting is implemented.
>>>
>>>
>
>This question was asked during PhpPgAdmin development. The answer is that "set
>client_encoding" is not always safe.
>
>For example:
>- server = SJSS
>- client = Unicode
>= mostly safe
>
>- server = Latin1
>- client = Unicode
>= not safe, because if you enter some non-regular characters, they will be
>dropped during conversion.
>
OK, this means a client encoding per database is needed, right?
Additional property for database?

Regards,
Andreas