plperl fixes

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: plperl fixes
Date: 2004-07-07 16:04:02
Message-ID: 40EC1EF2.1010201@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


The attached patch, which incorporates the previous one sent and
currently unapplied regarding spi_internal.c, makes some additional
fixes relating to return types, and also contains the fix for
preventing the use of insecure versions of Safe.pm.

There is one remaing return case that does not appear to work, namely
return of a composite directly in a select, i.e. if foo returns some
composite type, 'select * from foo()' works but 'select foo()' doesn't.
We will either fix that or document it as a limitation.

The function plperl_func_handler is a mess - I will try to get it
cleaned up (and split up) in a subsequent patch, time permitting.

Also, reiterating previous advice - this changes slightly the API for
spi_exec_query - the returned object has either 2 or 3 members: 'status'
(string) and 'proceesed' (int,- number of rows) and, if rows are
returned, 'rows' (array of tuple hashes).

cheers

andrew

Attachment Content-Type Size
plperl-patch text/plain 11.5 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Kris Jurka 2004-07-08 06:46:25 Re: ResultSerMetaData.getColumnDisplaySize() with timestamp
Previous Message Bruce Momjian 2004-07-07 12:50:21 Re: First attempt: support for '\dg' in psql