Re: plperlu problem with utf8

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: David Christensen <david(at)endpoint(dot)com>
Cc: "David E(dot) Wheeler" <david(at)kineticode(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-22 04:19:51
Message-ID: AANLkTineVH=mX-H4_8nJSjZxssaWiZR4KCQwj9kKoRG6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 20, 2010 at 00:39, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:

> In further review over caffeine this morning I noticed there are a few
> places I missed: plperl_build_tuple_result(), plperl_modify_tuple()
> and Util.XS.

And here is v3, fixes the above and also makes sure to properly
encode/decode SPI arguments. Tested on a latin1 database with latin1
columns and utf8 with utf8 columns. Also passes make installcheck (of
course) and changes one or two things to make plperl.c warning free.

Attachment Content-Type Size
plperl_enc_v3.patch.gz application/x-gzip 8.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesper Krogh 2010-12-22 05:24:48 Re: The cost of visibillity testing? (gin-search)
Previous Message Tom Lane 2010-12-22 04:17:45 Re: strncmp->memcmp when we know the shorter length