From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Careful PL/Perl Release Not Required |
Date: | 2011-02-11 18:01:37 |
Message-ID: | AANLkTinudXQeMZpqLMxfxZqjRPGPGDkLrwmaQFOxLrn7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 11, 2011 at 10:44, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> On Fri, Feb 11, 2011 at 10:16, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> That *looks* like it is decoding the input string, which it is, but
> actually that will double utf8 encode your string. It does not seem to
> in this case because we are dealing with all ascii input. The trick
> here is its also telling perl to decode/treat the *output* string as
> utf8.
Urp, this is a bit of a fib. The problem is actual in plperl not perl
persay. Pre 9.1 we always fetched perls internal string *ignoring* the
utf8 flag. So if you had octets that were utf8 things would work. The
utf8::decode($_[0]); uri_unescape($_[0]); happened to make the return
string internally be utf8 and so it would only return 1 char. Thats
what the op wanted and why it seemed to fix his problem. But thats
actually a bug! utf8::decode($_[0]) should not have changed anything
at all on the output side. It should still have returned 2 characters
instead of 1.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-02-11 18:02:20 | Re: Range Types: << >> -|- ops vs empty range |
Previous Message | Andrew Dunstan | 2011-02-11 17:53:15 | Re: Range Types: << >> -|- ops vs empty range |