| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | David Christensen <david(at)endpoint(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperlu problem with utf8 |
| Date: | 2010-12-20 00:56:55 |
| Message-ID: | CA0DD9F0-67D9-4467-AF6F-73285AA61F7D@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 19, 2010, at 12:20 AM, Alex Hunsaker wrote:
>> I would argue that it should output the same as the first example. That is, PL/Perl should have decoded the latin-1 before passing the text to the Perl function.
>
> Yeah, I don't think you will find anyone who disagrees :) PL/TCL and
> PL/Python get this right FWIW. Anyway find attached a patch that does
> just this.
>
> With the attached we:
<intelligent fixes elided />
+1 Awesome. Should this go into the next commitfest? Or might it be considered a bug fix?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2010-12-20 01:12:27 | Re: Serializable lock consistency (was Re: CommitFest wrap-up) |
| Previous Message | Tomas Vondra | 2010-12-20 00:46:06 | Re: keeping a timestamp of the last stats reset (for a db, table and function) |