3 Commits (0cb0ec9ed911eb423047c602b17284222abdfcc7)

Author	SHA1	Message	Date
Neil Conway	2b8afe6193	Tweak the error message emitted when a void-returning PL/Python function ... does not return None, per suggestion from Tom.	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
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
Tom Lane	00aa8ed47a	Adjust plpython to convert \r\n and \r to \n in Python scripts, ... per recent discussion concluding that this is the Right Thing. Add regression test check for this behavior. Michael Fuhr	21 years ago
Tom Lane	6115224448	Rename plpython to plpythonu, and update documentation to reflect its ... now-untrusted status.	23 years ago
Bruce Momjian	9b59ddfb40	It may not be obvious to you, but the plpython regression tests ... include output that vary depending on the python build one is running. Basically, the order of keys in a dictionary is non-deterministic, and that part of the test fails for me regularly. I rewrote the test to work around this problem, and include a patch file with that change and the change to the expected otuput as well. Mike Meyer	23 years ago
Bruce Momjian	1f653ec31e	I have attached two patches as per: ... 1) pltcl: Add SPI_freetuptable() calls to avoid memory leaks (Me + Neil Conway) Change sprintf()s to snprintf()s (Neil Conway) Remove header files included elsewhere (Neil Conway) 2)plpython: Add SPI_freetuptable() calls to avoid memory leaks Cosemtic change to remove a compiler warning Notes: I have tested pltcl.c for a) the original leak problem reported for the repeated call of spi_exec in a TCL fragment and b) the subsequent report resulting from the use of spi_exec -array in a TCL fragment. The plpython.c patch is exactly the same as that applied to make revision 1.23, the plpython_schema.sql and feature.expected sections of the patch are also the same as last submited, applied and subsequently reversed out. It remains untested by me (other than via make check). However, this should be safe provided PyString_FromString() _copies_ the given string to make a PyObject. Nigel J. Andrews	24 years ago
Bruce Momjian	72f8efdc98	Back out /pl memory leak patch. Wait for new version.	24 years ago
Bruce Momjian	b2c34e2bd1	I have attached the pltcl patch again, just in case. For the sake of clarity ... let's say this patch superscedes the previous one. I have also attached a patch addressing the similar memory leak problem in plpython. This includes a slight adjustment of the tests in the source directory. The patch also includes a cosmetic change to remove a compiler warning although I think the change makes the code look worse though. BTW, by my reckoning the memory leak would occur with prepared plans and without. If that is not the case then I've been barking up the wrong tree. Nigel J. Andrews	24 years ago
Bruce Momjian	7d5edf2ba7	Add new elog() levels to stored procedure languages. plperl DEBUG hack ... still needed because only removed in 7.4.	24 years ago
Bruce Momjian	06a8346c84	See attached for a small patch that enables plpython to build cleanly ... under Cygwin. This patch together with my previous Python patch: http://postgresql.readysetnet.com/mhonarc/pgsql-patches/2001-05/msg00075.htm l enables full Python support (i.e., configure --with-python) for Cygwin PostgreSQL. Jason Tishler	25 years ago
Peter Eisentraut	bbc3920fe9	PL/Python should build portably now, if you can get over the fact that ... there's no shared libpython. Test suite works as well. Also, add some documentation.	25 years ago
Bruce Momjian	0bef7ba549	Add plpython code.	25 years ago