Re: utf8 encoding problem with plperlu - Mailing list pgsql-general

From Ronald Peterson
Subject Re: utf8 encoding problem with plperlu
Date
Msg-id CAJPRK8ZF_UMCFiecq+KqRG-CSFxZWocaX7jdm3AwusSrj9Wsrg@mail.gmail.com
Whole thread Raw
In response to Re: utf8 encoding problem with plperlu  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Still trying to figure this out, still confused, but like most frustrating programming problems, I think I may be looking in the wrong place for the source of this error.  Perhaps.

On Wed, Jul 15, 2015 at 11:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ronald Peterson <ron@hub.yellowbank.com> writes:
> This does work for strings that don't contain consecutive zeroes.  I'm not
> really passing the string to PostgreSQL, but to Net::LDAP, but it must hit
> PostgreSQL anyway?  Active Directory requires this encoding, so I'm not
> sure what to do here.

Hm, well, the concrete example you showed involved passing the string to
elog(), which definitely will complain if what it's fed isn't legal data
according to the database encoding; as would any other attempt to push
data into the Postgres server environment.  I don't see why operations
that are strictly within Perl would have a problem, though.

                        regards, tom lane



--
-R-




pgsql-general by date:

Previous
From: Mitu Verma
Date:
Subject: Re: unexpected data beyond EOF in block 260 of relation pg_tblspc
Next
From: Michael Paquier
Date:
Subject: Re: Need help on postgres related to insertion of a tuple.