Re: pgadmin3 clientencoding

From: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
To: Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgadmin3 clientencoding
Date: 2003-06-10 07:30:42
Message-ID: 200306100930.42204.jm.poure@freesurf.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2003-06-10 07:34:13 Re: Howto Make?
Previous Message Jean-Michel POURE 2003-06-10 07:24:21 UTF-8 issues