From: Bill Willits <bwillits@cox.net>
To: pgsql-admin@postgresql.org
Subject: Character Corruption / Encoding Question
Date: Fri, 30 Nov 2007 12:07:40 -0800
Message-ID: <002601c8338c$aa2fb370$b501a8c0@bwlaptop> (raw)
We have just upgraded our phppgadmin client from v3.5 to v.4.1.3. Now, when we view special characters in phppgadmin they are displayed incorrectly. If we update the character field (to a special character), it will not store properly. Our database encoding is SQL_ASCII. The same operations work fine in v.3.5 of phppgadmin and with pgadmin III.
Obviously, this is a phppgadmin issue (and I have posted a question to them), but I am just curious what could have changed to cause it, and what if any workaround there would be outside of reverting to old version of phppgadmin or getting a patch.
Thanks
Bill Willits
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: bwillits@cox.net
Subject: Re: Character Corruption / Encoding Question
In-Reply-To: <002601c8338c$aa2fb370$b501a8c0@bwlaptop>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox