upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-02-21 00:40:20 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
postgresql/src/pl/plpython/expected/plpython_error_3.out

46 lines
2.3 KiB
Text
Raw Normal View History

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.
2006-11-21 16:51:05 -05:00
-- 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');
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.
2009-07-20 04:01:07 -04:00
WARNING: PL/Python: <class 'plpy.SPIError'>: unrecognized error in PLy_spi_prepare
CONTEXT: PL/Python function "invalid_type_uncaught"
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.
2006-11-21 16:51:05 -05:00
ERROR: type "test" does not exist
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "invalid_type_uncaught"
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.
2006-11-21 16:51:05 -05:00
SELECT invalid_type_caught('rick');
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.
2009-07-20 04:01:07 -04:00
WARNING: PL/Python: <class 'plpy.SPIError'>: unrecognized error in PLy_spi_prepare
CONTEXT: PL/Python function "invalid_type_caught"
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.
2006-11-21 16:51:05 -05:00
ERROR: type "test" does not exist
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "invalid_type_caught"
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.
2006-11-21 16:51:05 -05:00
SELECT invalid_type_reraised('rick');
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.
2009-07-20 04:01:07 -04:00
WARNING: PL/Python: <class 'plpy.SPIError'>: unrecognized error in PLy_spi_prepare
CONTEXT: PL/Python function "invalid_type_reraised"
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.
2006-11-21 16:51:05 -05:00
ERROR: type "test" does not exist
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "invalid_type_reraised"
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.
2006-11-21 16:51:05 -05:00
SELECT valid_type('rick');
valid_type
------------
(1 row)
--
-- Test Unicode error handling.
--
SELECT unicode_return_error();
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.
2009-07-20 04:01:07 -04:00
ERROR: PL/Python: could not create string representation of Python object, while creating return value
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.
2006-11-21 16:51:05 -05:00
DETAIL: <type 'exceptions.UnicodeEncodeError'>: 'ascii' codec can't encode character u'\x80' in position 0: ordinal not in range(128)
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "unicode_return_error"
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.
2006-11-21 16:51:05 -05:00
INSERT INTO unicode_test (testvalue) VALUES ('test');
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.
2009-07-20 04:01:07 -04:00
ERROR: PL/Python: could not compute string representation of Python object, while modifying trigger row
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.
2006-11-21 16:51:05 -05:00
DETAIL: <type 'exceptions.UnicodeEncodeError'>: 'ascii' codec can't encode character u'\x80' in position 0: ordinal not in range(128)
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "unicode_trigger_error"
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.
2006-11-21 16:51:05 -05:00
SELECT unicode_plan_error1();
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.
2009-07-20 04:01:07 -04:00
WARNING: PL/Python: <class 'plpy.Error'>: unrecognized error in PLy_spi_execute_plan
CONTEXT: PL/Python function "unicode_plan_error1"
ERROR: PL/Python: could not execute plan
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.
2006-11-21 16:51:05 -05:00
DETAIL: <type 'exceptions.UnicodeEncodeError'>: 'ascii' codec can't encode character u'\x80' in position 0: ordinal not in range(128)
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "unicode_plan_error1"
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.
2006-11-21 16:51:05 -05:00
SELECT unicode_plan_error2();
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.
2009-07-20 04:01:07 -04:00
ERROR: PL/Python: could not execute plan
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.
2006-11-21 16:51:05 -05:00
DETAIL: <type 'exceptions.UnicodeEncodeError'>: 'ascii' codec can't encode character u'\x80' in position 0: ordinal not in range(128)
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.
2009-07-20 04:01:07 -04:00
CONTEXT: PL/Python function "unicode_plan_error2"
Reference in a new issue Copy permalink