From bwillits@cox.net Fri Nov 30 20:07:57 2007 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-- From rossacher@bluewin.ch Fri Nov 30 22:05:51 2007 Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id D6DBE2E033F for ; Fri, 30 Nov 2007 18:05:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 64711-09 for ; Fri, 30 Nov 2007 18:05:43 -0400 (AST) Received: from mail21.bluewin.ch (mail21.bluewin.ch [195.186.18.66]) by postgresql.org (Postfix) with ESMTP id C471A2E016E for ; Fri, 30 Nov 2007 18:05:46 -0400 (AST) Received: from [192.168.1.74] (83.78.80.203) by mail21.bluewin.ch (Bluewin 7.3.121) id 471B45BE00B07957 for pgsql-admin@postgresql.org; Fri, 30 Nov 2007 22:05:45 +0000 From: Ivo Rossacher To: pgsql-admin@postgresql.org Subject: Re: Character Corruption / Encoding Question Date: Fri, 30 Nov 2007 23:05:44 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <002601c8338c$aa2fb370$b501a8c0@bwlaptop> In-Reply-To: <002601c8338c$aa2fb370$b501a8c0@bwlaptop> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711302305.44972.rossacher@bluewin.ch> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/268 X-Sequence-Number: 27511 Am Freitag, 30. November 2007 21.07:40 schrieb Bill Willits: > 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. SQL_ASCII is not an encoding but more the lack of any encoding support. This is required when you need full control of the encoding stuff. But then all the clients have to agree and take care by them self for the encoding. This can not be expected to be stable over several different applications, installations and releases and is therefore only usefull when really needed for some reason. So phpadmin would need to be configured to use the correct encoding for your setup (I do only have little, aged expirience with phpadmin but I think to remember that the encoding used is defined by the php installation). From my point of view it would make more sense to use UTF8 or any other encoding fullfilling your needs, so the database can convert the encoding from and to the client encoding for you. However depending of the actual status of the data in the database it might be some work to convert the data to the new encoding (it depends on how many different encodings where used to enter data into the database). You can find more details on the matter in the manual in chapter 21. Best regards Ivo Rossacher > > 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