15 Commits (501255114d0266a599c2b52fdf15fe8cac0a4650)

Author	SHA1	Message	Date
Peter Eisentraut	9d9848668f	Split the plpython regression test into test cases arranged by topic, instead ... of the previous monolithic setup-create-run sequence, that was apparently inherited from a previous test infrastructure, but makes working with the tests and adding new ones weird.	17 years ago
Tom Lane	cd331e4b84	Defend against possible crash if a plpython function does not specify names ... for its arguments. Also add a regression test, since someone apparently changed every single plpython test case to use only named parameters; else we'd have noticed this sooner. Euler Taveira de Oliveira, per a report from Alvaro	17 years ago
Tom Lane	bdc7dd6799	Fix plpython to not get totally confused by OUT arguments. (It still doesn't ... support multiple OUT arguments, though.) Hannu Krosing	18 years ago
Peter Eisentraut	3e584e071b	Remove use of whrandom module, which was removed in Python 2.5.	19 years ago
Bruce Momjian	819f22a302	Allow PL/python to return composite types and result sets ... Sven Suursoho	20 years ago
Andrew Dunstan	51b40f03a4	Looks like the new plpython regression test fails on older pythons. See if this works.	20 years ago
Andrew Dunstan	0a269db9cf	Add table_name and table_schema to plpython trigger data, plus docs and regression test.	20 years ago
Bruce Momjian	c574106a66	Adjust plpython for escape_string_warning.	20 years ago
Bruce Momjian	bc0be355c8	Adjust PL regression tests for escape_string_warning.	20 years ago
Neil Conway	87daae1143	Allow PL/Python functions to return void, per gripe from James Robinson ... (I didn't use his patch, however). A void-returning PL/Python function must return None (from Python), which is translated into a void datum (and *not* NULL) for Postgres. I also added some regression tests for this functionality.	20 years ago
Bruce Momjian	37f11c3081	This patch addresses the problem mentioned in the "process crash ... when a plpython function returns unicode" thread: http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php In several places PL/Python was calling PyObject_Str() and then PyString_AsString() without checking if the former had returned NULL to indicate an error. PyString_AsString() doesn't expect a NULL argument, so passing one causes a segmentation fault. This patch adds checks for NULL and raises errors via PLy_elog(), which prints details of the underlying Python exception. The patch also adds regression tests for these checks. All tests pass on my Solaris 9 box running HEAD and Python 2.4.1. In one place the patch doesn't call PLy_elog() because that could cause infinite recursion; see the comment I added. I'm not sure how to test that particular case or whether it's even possible to get an error there: the value that the code should check is the Python exception type, so I wonder if a NULL value "shouldn't happen." This patch converts NULL to "Unknown Exception" but I wonder if an Assert() would be appropriate. The patch is against HEAD but the same changes should be applied to earlier versions because they have the same problem. The patch might not apply cleanly against earlier versions -- will the committer take care of little differences or should I submit different versions of the patch? Michael Fuhr	21 years ago
Bruce Momjian	2d6c375c5f	Back out patch. This should be done like other server-side languages. ... --------------------------------------------------------------------------- This patch allows the PL/Python module to do (SRF) functions. The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk	21 years ago
Bruce Momjian	af8756713f	This patch allows the PL/Python module to do (SRF) functions. ... The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk	21 years ago
Tom Lane	59ee9448a8	Remove read_file/write_file tests. These were originally intended to ... *fail*, to test that plpython didn't allow untrusted operations. When we changed plpython to plpythonu because python didn't actually have a secure sandbox mode, someone (probably me :-() misinterpreted the tests as checking whether Python's file I/O works. Which is a stupid thing for us to be testing. Remove it so we don't clutter the filesystem with random temporary files.	21 years ago
Tom Lane	0ff7a2c2ad	Convert the existing regression test scripts for the various optional ... PLs to use the standard pg_regress infrastructure. No changes in the tests themselves. Andrew Dunstan	21 years ago