Re: pgadmin3 clientencoding - Mailing list pgadmin-hackers

From Jean-Michel POURE
Subject Re: pgadmin3 clientencoding
Date
Msg-id 200306100930.42204.jm.poure@freesurf.fr
Whole thread Raw
In response to Re: pgadmin3 clientencoding  (Andreas Pflug <Andreas.Pflug@web.de>)
Responses Re: pgadmin3 clientencoding  (Andreas Pflug <Andreas.Pflug@web.de>)
List pgadmin-hackers
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.

Cheers,
Jean-Michel


pgadmin-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: UTF-8 issues
Next
From: Jean-Michel POURE
Date:
Subject: Re: Howto Make?