Theo Schlossnagle <[EMAIL PROTECTED]> writes:
> I've found a bug with the way plperl/plperlu handles bytea types. It
> fails to correctly handle bytea binary inputs and outputs.
Define "correctly". The proposed patch seems to be "let's handle
bytea differently from every other data type", and
what of made a mistake?
Date: Fri, 27 Apr 2007 20:01:23 -0300
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
estevam:~ # cd postgresql-8.2.4/
estevam:~/postgresql-8.2.4 # su - postgres
su: warning: cannot change directory to /var/lib/pgsql: No such file or
dire
I've found a bug with the way plperl/plperlu handles bytea types. It
fails to correctly handle bytea binary inputs and outputs. Perl
scalars are wrongly treated as C strings when a the source or
destination tuple in postgres is of type bytea.
The attached patch alters the code path for in
