Bruce Momjian 96b9dc1aef 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). Andrew Dunstan		2004-07-12 14:31:04 +00:00
..
plperl	The attached patch, which incorporates the previous one sent and	2004-07-12 14:31:04 +00:00
plpgsql	Okay, I've had it with answering newbie questions about why plpgsql	2004-07-04 02:49:04 +00:00
plpython	Infrastructure for I/O of composite types: arrange for the I/O routines	2004-06-06 00:41:28 +00:00
tcl	Infrastructure for I/O of composite types: arrange for the I/O routines	2004-06-06 00:41:28 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00