From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: plperlu problem with utf8 |
Date: | 2010-12-18 01:22:16 |
Message-ID: | B248634C-B273-4871-86F6-E809E9E4D41B@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Dec 17, 2010, at 5:04 PM, David E. Wheeler wrote:
>> see? Either uri_unescape() should be decoding that utf8() or you need
>> to do it *after* you call uri_unescape(). Hence the maybe it could be
>> considered a bug in uri_unescape().
>
> Agreed.
On second thought, no. You can in fact encode anything in a URI. URI::Escape can't know what to decode to. So *I believe* it just unescapes the raw bytes. It might be handy for it to have a new function, though, to complement its uri_escape_utf() function:
sub uri_unescape_utf8 { Encode::decode_utf8(uri_unescape(@_)) }
Just to make things a bit clearer.
But that's a separate issue from the, erm, inconsistency with which PL/Perl treats encoding and decoding of its inputs and outputs.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | andreas | 2010-12-18 01:34:54 | Tab completion for ALTER ... SET SCHEMA |
Previous Message | David E. Wheeler | 2010-12-18 01:04:47 | Re: plperlu problem with utf8 |