Re: Database->ServerEncoding, ClientEncoding (again) - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Database->ServerEncoding, ClientEncoding (again)
Date
Msg-id 1087.193.237.19.179.1014669028.squirrel@ssl.vale-housing.co.uk
Whole thread Raw
In response to Database->ServerEncoding, ClientEncoding (again)  (Jean-Michel POURE <jm.poure@freesurf.fr>)
Responses Re: Database->ServerEncoding, ClientEncoding (again)
List pgadmin-hackers
Jean-Michel POURE allegedly said:
> Hi Dave,
>
> Also, we need to set Schema->Encoding. This is to define what client
> encoding  is used for schema creation. For example, I would like to use
> Latin1 for  writing functions.

As I said in my previous message, we can only set it once for each
database, otherwise it will become unpredictable as you jump from window
to window.

The only other option I can think of, would be to open a dedicated
connection for each SQL window, but this would:

a) waste resources.
b) bypass logging, query recording etc. in pgSchema (definately not
acceptable).

Regards, Dave.



pgadmin-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Database->ServerEncoding, ClientEncoding
Next
From: Jean-Michel POURE
Date:
Subject: Re: Database->ServerEncoding, ClientEncoding