diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2009-08-12 16:37:26 +0000 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2009-08-12 16:37:26 +0000 |
| commit | 9d9848668fd868a4e51f3a3f22c2807ff0e46582 (patch) | |
| tree | 22b0152fb889ca42d3e4c6ce888d2024b8b8c98b /src/pl/plpython/expected/plpython_error_1.out | |
| parent | ef7574eb014b66d99a5e68cc254e7a2282e69a00 (diff) | |
| download | postgresql-9d9848668fd868a4e51f3a3f22c2807ff0e46582.tar.gz | |
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.
Diffstat (limited to 'src/pl/plpython/expected/plpython_error_1.out')
| -rw-r--r-- | src/pl/plpython/expected/plpython_error_1.out | 38 |
1 files changed, 0 insertions, 38 deletions
diff --git a/src/pl/plpython/expected/plpython_error_1.out b/src/pl/plpython/expected/plpython_error_1.out deleted file mode 100644 index e36b8650a3..0000000000 --- a/src/pl/plpython/expected/plpython_error_1.out +++ /dev/null @@ -1,38 +0,0 @@ --- test error handling, i forgot to restore Warn_restart in --- the trigger handler once. the errors and subsequent core dump were --- interesting. -SELECT invalid_type_uncaught('rick'); -WARNING: PL/Python: in PL/Python function "invalid_type_uncaught" -DETAIL: plpy.SPIError: unrecognized error in PLy_spi_prepare -ERROR: type "test" does not exist -SELECT invalid_type_caught('rick'); -WARNING: PL/Python: in PL/Python function "invalid_type_caught" -DETAIL: plpy.SPIError: unrecognized error in PLy_spi_prepare -ERROR: type "test" does not exist -SELECT invalid_type_reraised('rick'); -WARNING: PL/Python: in PL/Python function "invalid_type_reraised" -DETAIL: plpy.SPIError: unrecognized error in PLy_spi_prepare -ERROR: type "test" does not exist -SELECT valid_type('rick'); - valid_type ------------- - -(1 row) - --- --- Test Unicode error handling. --- -SELECT unicode_return_error(); -ERROR: PL/Python: could not create string representation of Python object in PL/Python function "unicode_return_error" while creating return value -DETAIL: exceptions.UnicodeEncodeError: 'ascii' codec can't encode character '\u80' in position 0: ordinal not in range(128) -INSERT INTO unicode_test (testvalue) VALUES ('test'); -ERROR: PL/Python: could not compute string representation of Python object in PL/Python function "unicode_trigger_error" while modifying trigger row -DETAIL: exceptions.UnicodeEncodeError: 'ascii' codec can't encode character '\u80' in position 0: ordinal not in range(128) -SELECT unicode_plan_error1(); -WARNING: PL/Python: in PL/Python function "unicode_plan_error1" -DETAIL: plpy.Error: unrecognized error in PLy_spi_execute_plan -ERROR: PL/Python: PL/Python function "unicode_plan_error1" could not execute plan -DETAIL: exceptions.UnicodeEncodeError: 'ascii' codec can't encode character '\u80' in position 0: ordinal not in range(128) -SELECT unicode_plan_error2(); -ERROR: PL/Python: PL/Python function "unicode_plan_error2" could not execute plan -DETAIL: exceptions.UnicodeEncodeError: 'ascii' codec can't encode character '\u80' in position 0: ordinal not in range(128) |