Re: Database->ServerEncoding, ClientEncoding

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Database->ServerEncoding, ClientEncoding
Date: 2002-02-26 12:43:54
Message-ID: FED2B709E3270E4B903EB0175A49BCB1047621@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 26 February 2002 12:09
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Database->ServerEncoding,
> ClientEncoding
>
>
> Le Mardi 26 Février 2002 12:20, Dave Page a écrit :
> > That will work for System stuff. On the User/Data side,
> those queries
> > *only* come from frmSQLInput or a 'View Data' (iirc). For
> these types
> > of query, *if* we had a second connection to the database, then it
> > could maintain it's client encoding neatly as well.
>
> Is encoding set by connection? Cheers/JMP

Yes, we would have one connection for the System stuff, and one for
User/Data. That way, there's no need to keep changing the encoding, only
when the user manually changes it or upon initial connection.

/D

Browse pgadmin-hackers by date

  From Date Subject
Next Message Henshall, Stuart - WCP 2002-02-26 12:46:41 Re: [ODBC] pgAdmin2 Japanese display
Previous Message Dave Page 2002-02-26 12:39:06 Re: [ODBC] pgAdmin2 Japanese display