Re: UTF-8 encoding problem w/ libpq

From: Martin Schäfer <Martin(dot)Schaefer(at)cadcorp(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UTF-8 encoding problem w/ libpq
Date: 2013-06-10 07:08:15
Message-ID: 11A8567A97B15648846060F5CD818EB8CAC2253F82@DEV001EX.Dev.cadcorp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks Andrew. I will test the next release.

Martin

> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
> Sent: 08 June 2013 16:43
> To: Tom Lane
> Cc: Heikki Linnakangas; ktm(at)rice(dot)edu; Martin Schäfer; pgsql-
> hackers(at)postgresql(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-06-10 08:05:40 Re: Optimising Foreign Key checks
Previous Message Andrew Dunstan 2013-06-10 06:16:12 Re: JSON and unicode surrogate pairs