Re: utf8 encoding problem with plperlu

From: Ronald Peterson <ron(at)hub(dot)yellowbank(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: utf8 encoding problem with plperlu
Date: 2015-07-16 12:14:47
Message-ID: CAJPRK8ZF_UMCFiecq+KqRG-CSFxZWocaX7jdm3AwusSrj9Wsrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Ronald Peterson <ron(at)hub(dot)yellowbank(dot)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-

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2015-07-16 13:09:39 Re: Need help on postgres related to insertion of a tuple.
Previous Message Mitu Verma 2015-07-16 10:10:43 Re: unexpected data beyond EOF in block 260 of relation pg_tblspc