| 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> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: [ODBC] pgAdmin2 UTF-8 support |
| Date: | 2002-02-25 08:46:57 |
| Message-ID: | FED2B709E3270E4B903EB0175A49BCB10475F9@dogbert.vale-housing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 25 February 2002 08:39
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> Le Lundi 25 Février 2002 09:29, Dave Page a écrit :
> > SET CLIENT_ENCODING Latin1;
> > INSERT INTO table_foo (field_bar) VALUES ('é'); SELECT
> field_bar FROM
> > table_foo WHERE field_bar='é';
>
> In case of an UTF-8 database,
> - schema queries should always be sent in Latin1.
> - SQL highlightbox should allow to choose client encoding on
> the fly in a
> combo.
>
> How do we query current client encoding?
SHOW CLIENT_ENCODING;
However the result is returned as a NOTICE message from the backend so we'd
have to do it via low level ODBC API calls (checkout how EXPLAIN works for
an example).
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-02-25 08:51:04 | Re: [ODBC] pgAdmin2 UTF-8 support |
| Previous Message | Dave Page | 2002-02-25 08:42:35 | Re: [ODBC] pgAdmin2 UTF-8 support |