postgresql/src/pl/plpython/sql/plpython_do.sql

DO $$ plpy.notice("This is plpythonu.") $$ LANGUAGE plpythonu;

DO $$ plpy.notice("This is plpython2u.") $$ LANGUAGE plpython2u;

DO $$ raise Exception("error test") $$ LANGUAGE plpythonu;
PL/Python DO handler Also cleaned up some redundancies between the primary error messages and the error context in PL/Python. Hannu Valtonen 2010-01-22 10:45:15 -05:00			`DO $$ plpy.notice("This is plpythonu.") $$ LANGUAGE plpythonu;`

PL/Python: Improve test coverage Add test cases for inline handler of plython2u (when using that language name), and for result object element assignment. There is now at least one test case for every top-level functionality, except plpy.Fatal (annoying to use in regression tests) and result object slice retrieval and slice assignment (which are somewhat broken). 2012-05-02 14:09:03 -04:00			`DO $$ plpy.notice("This is plpython2u.") $$ LANGUAGE plpython2u;`

PL/Python: Adjust the regression tests for Python 3.4 The error test case in the plpython_do test resulted in a slightly different error message with Python 3.4. So pick a different way to test it that avoids that and is perhaps also a bit clearer. 2014-04-29 22:16:16 -04:00			`DO $$ raise Exception("error test") $$ LANGUAGE plpythonu;`