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:42:35 |
Message-ID: | FED2B709E3270E4B903EB0175A49BCB10475F8@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: 25 February 2002 08:30
> 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 :
> > Presumably we should do this in SQL (I don't think you can do it in
> > the ODBC connect string can you?). Have you tried in pgAdmin:
> >
> > SET CLIENT_ENCODING Latin1;
> > INSERT INTO table_foo (field_bar) VALUES ('é'); SELECT
> field_bar FROM
> > table_foo WHERE field_bar='é';
>
> I just tried it, it works !!!
> Apache + Php display the 'é'.
OK, what about if you select the data back in pgAdmin - does it then display
it?
Also, does SET CLIENT_ENCODING SQL_ASCII; work?
regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2002-02-25 08:46:57 | Re: [ODBC] pgAdmin2 UTF-8 support |
Previous Message | Jean-Michel POURE | 2002-02-25 08:38:48 | Re: [ODBC] pgAdmin2 UTF-8 support |