Re: UTF-8 encoding problem w/ libpq - Mailing list pgsql-hackers

From Martin Schäfer
Subject Re: UTF-8 encoding problem w/ libpq
Date
Msg-id 11A8567A97B15648846060F5CD818EB8CAC2253F82@DEV001EX.Dev.cadcorp.net
Whole thread Raw
In response to Re: UTF-8 encoding problem w/ libpq  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Thanks Andrew. I will test the next release.

Martin

> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> Sent: 08 June 2013 16:43
> To: Tom Lane
> Cc: Heikki Linnakangas; ktm@rice.edu; Martin Schäfer; pgsql-
> hackers@postgresql.org
> Subject: Re: [HACKERS] UTF-8 encoding problem w/ libpq
>
>
> On 06/03/2013 02:41 PM, Andrew Dunstan wrote:
> >
> > On 06/03/2013 02:28 PM, Tom Lane wrote:
> >> . I wonder though if we couldn't just fix this code to not do
> >> anything to high-bit-set bytes in multibyte encodings.
> >
> >
> > That's exactly what I suggested back in November.
>
>
> This thread seems to have gone cold, so I have applied the fix I originally
> suggested along these lines to all live branches.
>
> At least that means we won't produce junk, but we still need to work out
> how to downcase multi-byte characters.
>
> If anyone thinks there are other places in the code that need similar
> treatment, they are welcome to find them. I have not yet found one.
>
>
> cheers
>
> andrew
>




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: JSON and unicode surrogate pairs
Next
From: Simon Riggs
Date:
Subject: Re: Optimising Foreign Key checks