Re: [ODBC] UTF-8 support

> -----Original Message-----
> From: Tatsuo Ishii [mailto:t-ishii@sra.co.jp]
> Sent: 24 September 2001 08:13
> To: sa_mokho@alcor.concordia.ca
> Cc: jm.poure@freesurf.fr; pgsql-odbc@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [ODBC] [HACKERS] UTF-8 support
>
>
> > Which ones belong to the backend and which ones to the frontend? Or
> > even more: which ones belong to the backend, which ones to the
> > frontend #1, which ones to the frontend #2, etc...
> >
> > For examle, I have two fronends:
> >
> > FE1: UNICODE,  WIN1251
> > FE2: KOI8, UNICODE
> > BE: UNICODE, LATIN1, ALT
> >
> > Which ones SELECT pg_available_encodings(); will show?
> > The ones of the BE and the FE making the request?
> >
> > In case I need to communicate with BE using one common encoding
> > between the two if it is available.
>
> I'm confused.
>
> What do you mean by BE? BE's encoding is determined by the
> database that FE chooses. If you just want to know what kind
> encodings are there in the database, why not use:
>
> SELECT DISTINCT ON (encoding) pg_encoding_to_char(encoding)
> AS encoding FROM pg_database;
>
> Also, FE's encoding could be any valid encoding that FE
> chooses, i.e. it' not BE's choice.
>
> Can you show me more concrete examples showing what you
> actually want to do?
>
> >> 3) Is there a way to query available encodings in PostgreSQL for
> >> display in pgAdmin.
> >
> > Could pgAdmin display multibyte chars in the first place ?
>
> Wao. If pgAdmin could not display multibyte chars, all
> discussions here are meaningless:-<

Apparently it can, I just don't know how to do it yet! From what
Jean-Michel's said, it's just a case of kicking VB6 in the right part of the
anatomy...

Regards, Dave.