4 Commits (c6ea8ccea6bf23501962ddc7ac9ffdb99c8643e1)

Author	SHA1	Message	Date
Peter Eisentraut	5809a64584	Set client encoding explicitly in plpython_unicode test ... This will (hopefully) eliminate the need for the plpython_unicode_0.out expected file.	15 years ago
Peter Eisentraut	4ab6ebf3f4	Add Unicode support in PL/Python ... PL/Python now accepts Unicode objects where it previously only accepted string objects (for example, as return value). Unicode objects are converted to the PostgreSQL server encoding as necessary. This change is also necessary for future Python 3 support, which treats all strings as Unicode objects. Since this removes the error conditions that the plpython_unicode test file tested for, the alternative result files are no longer necessary.	17 years ago
Peter Eisentraut	27c405d61a	Enhanced error context support in PL/Python ... Extract the "while creating return value" and "while modifying trigger row" parts of some error messages into another layer of error context. This will simplify the upcoming patch to improve data type support, but it can stand on its own.	17 years ago
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
Peter Eisentraut	5106bdc450	Use errcontext mechanism in PL/Python ... Error messages from PL/Python now always mention the function name in the CONTEXT: field. This also obsoletes the few places that tried to do the same manually. Regression test files are updated to work with Python 2.4-2.6. I don't have access to older versions right now.	17 years ago
Peter Eisentraut	1fb1049836	plpython_error.out is for Python 2.4, plpython_error_3.out is for Python 2.5, ... as it was previously.	17 years ago
Tom Lane	c714e5cba7	Fix plpython to work (or at least pass its regression tests) with ... python 2.5. This involves fixing several violations of the published spec for creating PyTypeObjects, and adding another regression test expected output for yet another variation of error message spelling.	19 years ago
Tom Lane	1e6201a22c	Add an expected case to cover error message as spelled by python 2.2.3. ... Per buildfarm results and Michael Fuhr.	21 years ago
Tom Lane	a8a3c3c4d6	Add variant expected file to cope with different spelling of a Python ... error message in Python 2.3 and before. Per Michael Fuhr and buildfarm results.	21 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
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
Tom Lane	5f2499d5af	Update to match error editing.	23 years ago
Tom Lane	6115224448	Rename plpython to plpythonu, and update documentation to reflect its ... now-untrusted status.	23 years ago
Tom Lane	6f49703f0e	Clean up plpython error reporting so that its regression test passes ... with some amount of cleanliness. I see no need to report the internal Python name rather than the SQL procedure name in error tracebacks.	23 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
Tom Lane	1ca717f377	plpython security and error handling fixes, from ... Kevin Jacobs and Brad McLean.	24 years ago
Bruce Momjian	0bef7ba549	Add plpython code.	25 years ago