Re: BUG #5869: postgresql corrupts unquoted non-ascii chars in column aliases - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5869: postgresql corrupts unquoted non-ascii chars in column aliases
Date
Msg-id AANLkTimbEbniiq2SuGHbtj9EvsCjsBLJxGKu9RFTiFpJ@mail.gmail.com
Whole thread Raw
In response to BUG #5869: postgresql corrupts unquoted non-ascii chars in column aliases  ("David Schmitt" <david@dasz.at>)
List pgsql-bugs
On Thu, Mar 3, 2011 at 11:51 AM, David Schmitt <david@dasz.at> wrote:
> On 03.03.2011 16:08, Robert Haas wrote:
>>
>> On Tue, Feb 8, 2011 at 2:19 AM, David Schmitt<david@dasz.at> =A0wrote:
>>>
>>> Example query:
>>>
>>> =A0SELECT column as zur=FCck FROM table;
>>>
>>> results in corruption of the "=FC" (umlaut u). This causes Npgsql to fa=
il
>>> to
>>> match up the columns in the result set (see
>>>
>>> http://pgfoundry.org/tracker/?func=3Ddetail&aid=3D1010988&group_id=3D10=
00140&atid=3D
>>> 590) and pgadminIII doesn't display the alias in the result pane.
>>
>> That link doesn't show anything interesting when I look at it. =A0What
>> exactly do you mean by corrupted?
>
> There are some garbage bytes instead of the umlaut.

I'm not really an encoding guy, but I would think that someone who is
would want to know exactly what bytes you were ending up with.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Corrupted index on 9.0.3 streaming hot standby
Next
From: Tom Lane
Date:
Subject: Re: can't build contrib/uuid-ossp