From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [ODBC] pgAdmin2 UTF-8 support |
Date: | 2002-02-25 08:18:14 |
Message-ID: | 200202250818.g1P8IEFP007742@www1.translationforge |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-odbc |
Dear Dave,
I used pgsql with PostgreSQL 7.2 and noticed there was an automatic
translation between UTF-8 <-> Latin characters. This is a new feature of
PostgreSQL 7.2.
So fine :
Suppose we have a Unicode database :
\Encoding Latin1 (\same with \Encoding SQL_ASCII does not work)
INSERT INTO table_foo (field_bar) VALUES ('é');
SELECT field_bar FROM table_foo WHERE field_bar='é' works.
I checked the UTF-8 display in Apache, it works.
In the case of an UTF-8 database, it means we need to create and query schema
objects using \Encoding Latin1. Should it be done at ODBC level or at
pgAdmin2 level? What is your opinion?
This could help us display non-multibyte UTF-8 data as well.
Cheers,
Jean-Michel POURE
From | Date | Subject | |
---|---|---|---|
Next Message | Dannyi@barak.net.il | 2002-02-25 08:22:20 | Re: [ODBC] pgAdmin2 UTF-8 support |
Previous Message | Dave Page | 2002-02-25 08:14:31 | Re: Working oin pgAdmin2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Dannyi@barak.net.il | 2002-02-25 08:22:20 | Re: [ODBC] pgAdmin2 UTF-8 support |
Previous Message | Jean-Michel POURE | 2002-02-24 21:39:14 | pgAdmin2 UTF-8 support |