On Fri, Dec 14, 2012 at 10:46 AM, Baptiste GONOD
<baptiste.gonod@gmail.com> wrote:
> Ok that's a front-end. My problem isn't with my website.. he's work fine in
> utf8 with postgreSQL in utf8 - tested with pg_connect or odbc connection.
OK.
> PgAdmin is a front-end too, not ?! And it's pgadmin that doesn't display
> data in utf8. All is encoded in WIN1252 whereas all settings are
> utf8/unicode in all options.
You said your database was UTF-8. So where does WIN1252 come into
this? If the database is in UTF-8, pgAdmin uses UTF-8 internally,
there should never be any WIN1252 involved at all.
> More, phppgadmin has the same problem. So we could conclude that my database
> isn't in utf8, but postgreSQL say no.
If phpPgAdmin has the same issue, than that also implies there's
something getting messed up in your front end, that causing data to be
stored differently than you expect. Both pgAdmin and phpPgAdmin have
been used for 10+ years by hundreds of thousands of people with UTF-8
data.
> So, pgadmin and phpadmin use the same device to collect data ? And this is
> the way which wrong ?
The only common thing between them is libpq - which is also used by
psql, pg_dump, pg_restore etc. It's even more tried and tested than
the admin tools, as every single PostgreSQL installation there is
relies on it.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
