Re: utf8 encoding problem with plperlu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ron(at)yellowbank(dot)com
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: utf8 encoding problem with plperlu
Date: 2015-07-16 03:25:08
Message-ID: 20431.1437017108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guillaume Lelarge 2015-07-16 05:03:01 Re: EXCLUDE, Gist and integers
Previous Message Ken Tanzer 2015-07-16 00:21:07 EXCLUDE, Gist and integers