| From: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
|---|---|
| To: | jm(dot)poure(at)freesurf(dot)fr, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: pgadmin3 clientencoding |
| Date: | 2003-06-10 09:39:29 |
| Message-ID: | 3EE5A751.7030601@web.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2003-06-10 10:10:00 | Re: [Fwd: pgadmin3 clientencoding] |
| Previous Message | Jean-Michel POURE | 2003-06-10 09:16:08 | pgAdmin3 RedHat binaries available |