The following short function illustrates a problem I'm having with the
plperlu module.
CREATE OR REPLACE FUNCTION
doublezero ()
RETURNS VOID
AS $$
use Encode qw/encode decode/;
$pass = "double00";
elog( INFO, "$pass" );
$mspass = encode( 'UTF-16LE', qq("$pass") );
elog( INFO, "$mspass" );
$$ LANGU
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.
On Wed, Jul 15, 2015 at 11:57 AM, Daniel Verite
wrote:
> Ronald Peterson wr
Thanks Pavel, this looks promising. I didn't know about the Data::Peek
module - that might help me figure out what is going on.
On Wed, Jul 15, 2015 at 2:28 PM, Pavel Stehule
wrote:
>
>
> 2015-07-15 20:20 GMT+02:00 Ronald Peterson :
>
>> That's interesting. What
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 wrote:
> Ronald Peterson writes:
> > This does work for str
I added a 'raise notice' to a plpgsql function I was working on
recently, and noticed that my notification was being raised more often
than I expected. The notification is raised in a function ('getone'
in my example below) that returns a single composite value. This
function is then called by an
I added a 'raise notice' to a plpgsql function I was working on
recently, and noticed that my notification was being raised more often
than I'd expect. The notification is raised in a function ('getone'
in my example below) that returns a single composite value. This
function is then called by an
obably only concerns me.
On Mon, Dec 29, 2014 at 10:54 AM, Tom Lane wrote:
> Ronald Peterson writes:
> > I added a 'raise notice' to a plpgsql function I was working on
> > recently, and noticed that my notification was being raised more often
> > than I expected. The
