postgresql/src/pl/plpython/expected/plpython_error.out

-- 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:  plpython: in function invalid_type_uncaught:
DETAIL:  plpy.SPIError: Unknown error in PLy_spi_prepare
ERROR:  type "test" does not exist
SELECT invalid_type_caught('rick');
WARNING:  plpython: in function invalid_type_caught:
DETAIL:  plpy.SPIError: Unknown error in PLy_spi_prepare
ERROR:  type "test" does not exist
SELECT invalid_type_reraised('rick');
WARNING:  plpython: in function invalid_type_reraised:
DETAIL:  plpy.SPIError: Unknown error in PLy_spi_prepare
ERROR:  type "test" does not exist
SELECT valid_type('rick');
 valid_type 
------------
 
(1 row)
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 2005-05-14 13:55:22 -04:00			`-- test error handling, i forgot to restore Warn_restart in`
			`-- the trigger handler once. the errors and subsequent core dump were`
			`-- interesting.`
Add plpython code. 2001-05-09 15:54:38 -04:00			`SELECT invalid_type_uncaught('rick');`
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. 2003-01-31 17:25:14 -05:00			`WARNING: plpython: in function invalid_type_uncaught:`
Update to match error editing. 2003-07-25 20:02:02 -04:00			`DETAIL: plpy.SPIError: Unknown error in PLy_spi_prepare`
			`ERROR: type "test" does not exist`
Add plpython code. 2001-05-09 15:54:38 -04:00			`SELECT invalid_type_caught('rick');`
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. 2003-01-31 17:25:14 -05:00			`WARNING: plpython: in function invalid_type_caught:`
Update to match error editing. 2003-07-25 20:02:02 -04:00			`DETAIL: plpy.SPIError: Unknown error in PLy_spi_prepare`
			`ERROR: type "test" does not exist`
Add plpython code. 2001-05-09 15:54:38 -04:00			`SELECT invalid_type_reraised('rick');`
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. 2003-01-31 17:25:14 -05:00			`WARNING: plpython: in function invalid_type_reraised:`
Update to match error editing. 2003-07-25 20:02:02 -04:00			`DETAIL: plpy.SPIError: Unknown error in PLy_spi_prepare`
			`ERROR: type "test" does not exist`
Add plpython code. 2001-05-09 15:54:38 -04:00			`SELECT valid_type('rick');`
			`valid_type`
			`------------`

			`(1 row)`