Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 6DCC42E0046 for ; Fri, 30 Nov 2007 16:07:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 59927-02 for ; Fri, 30 Nov 2007 16:07:52 -0400 (AST) Received: from fed1rmmtao107.cox.net (fed1rmmtao107.cox.net [68.230.241.39]) by postgresql.org (Postfix) with ESMTP id 1F9762E3A2A for ; Fri, 30 Nov 2007 16:07:53 -0400 (AST) Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20071130200753.PVOW2243.fed1rmmtao107.cox.net@fed1rmimpo01.cox.net> for ; Fri, 30 Nov 2007 15:07:53 -0500 Received: from bwlaptop ([68.101.98.29]) by fed1rmimpo01.cox.net with bizsmtp id K87k1Y0070e2M1w0000000; Fri, 30 Nov 2007 15:07:52 -0500 Message-ID: <002601c8338c$aa2fb370$b501a8c0@bwlaptop> From: "Bill Willits" To: Subject: Character Corruption / Encoding Question Date: Fri, 30 Nov 2007 12:07:40 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0023_01C83349.9B1939D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/253 X-Sequence-Number: 27496 This is a multi-part message in MIME format. ------=_NextPart_000_0023_01C83349.9B1939D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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. =20 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 ------=_NextPart_000_0023_01C83349.9B1939D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
We have just upgraded our phppgadmin = client from=20 v3.5 to v.4.1.3.  Now, when we view special characters in = phppgadmin they=20 are displayed incorrectly.  If we update the character field (to a = special=20 character), it will not store properly.  Our database encoding is=20 SQL_ASCII.  The same operations work fine in v.3.5 of phppgadmin = and with=20 pgadmin III. 
 
Obviously, this is a phppgadmin issue = (and I have=20 posted a question to them), but I am just curious what could have = changed to=20 cause it, and what if any workaround there would be outside of reverting = to old=20 version of phppgadmin or getting a patch.
 
Thanks
Bill Willits
------=_NextPart_000_0023_01C83349.9B1939D0--