From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Database->ServerEncoding, ClientEncoding |
Date: | 2002-02-26 09:39:47 |
Message-ID: | 200202260939.g1Q9dlLx009171@www1.translationforge |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Le Mardi 26 Février 2002 09:46, Dave Page a écrit :
> I forgot I added the query types (that was a recent change to support the
> session recorder). Something like that will probably do it, yes. From a
> sensible user interface point of view, you could select the system encoding
> when logging on (that would be server-wide - would that be a problem), and
> the data/user encoding from the SQL window, but default to the system
> encoding if a different selection has never been made.
Hmm, you are right, now I understand that client encoding is set for all
databases... because it is a PostgreSQL variable.
This solution works for me. Shall I add pgServer->ClientEncoding?
Cheers,
Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-26 09:43:30 | Re: Database->ServerEncoding, ClientEncoding |
Previous Message | Jean-Michel POURE | 2002-02-26 09:27:58 | Re: fake vs real CREATE OR REPLACE VIEW |