-- test error handling, i forgot to restore Warn_restart in -- the trigger handler once. the errors and subsequent core dump were -- interesting. /* Flat out Python syntax error */ CREATE FUNCTION python_syntax_error() RETURNS text AS '.syntaxerror' LANGUAGE plpythonu; /* With check_function_bodies = false the function should get defined * and the error reported when called */ SET check_function_bodies = false; CREATE FUNCTION python_syntax_error() RETURNS text AS '.syntaxerror' LANGUAGE plpythonu; SELECT python_syntax_error(); /* Run the function twice to check if the hashtable entry gets cleaned up */ SELECT python_syntax_error(); RESET check_function_bodies; /* Flat out syntax error */ CREATE FUNCTION sql_syntax_error() RETURNS text AS 'plpy.execute("syntax error")' LANGUAGE plpythonu; SELECT sql_syntax_error(); /* check the handling of uncaught python exceptions */ CREATE FUNCTION exception_index_invalid(text) RETURNS text AS 'return args[1]' LANGUAGE plpythonu; SELECT exception_index_invalid('test'); /* check handling of nested exceptions */ CREATE FUNCTION exception_index_invalid_nested() RETURNS text AS 'rv = plpy.execute("SELECT test5(''foo'')") return rv[0]' LANGUAGE plpythonu; SELECT exception_index_invalid_nested(); /* a typo */ CREATE FUNCTION invalid_type_uncaught(a text) RETURNS text AS 'if "plan" not in SD: q = "SELECT fname FROM users WHERE lname = $1" SD["plan"] = plpy.prepare(q, [ "test" ]) rv = plpy.execute(SD["plan"], [ a ]) if len(rv): return rv[0]["fname"] return None ' LANGUAGE plpythonu; SELECT invalid_type_uncaught('rick'); /* for what it's worth catch the exception generated by * the typo, and return None */ CREATE FUNCTION invalid_type_caught(a text) RETURNS text AS 'if "plan" not in SD: q = "SELECT fname FROM users WHERE lname = $1" try: SD["plan"] = plpy.prepare(q, [ "test" ]) except plpy.SPIError, ex: plpy.notice(str(ex)) return None rv = plpy.execute(SD["plan"], [ a ]) if len(rv): return rv[0]["fname"] return None ' LANGUAGE plpythonu; SELECT invalid_type_caught('rick'); /* for what it's worth catch the exception generated by * the typo, and reraise it as a plain error */ CREATE FUNCTION invalid_type_reraised(a text) RETURNS text AS 'if "plan" not in SD: q = "SELECT fname FROM users WHERE lname = $1" try: SD["plan"] = plpy.prepare(q, [ "test" ]) except plpy.SPIError, ex: plpy.error(str(ex)) rv = plpy.execute(SD["plan"], [ a ]) if len(rv): return rv[0]["fname"] return None ' LANGUAGE plpythonu; SELECT invalid_type_reraised('rick'); /* no typo no messing about */ CREATE FUNCTION valid_type(a text) RETURNS text AS 'if "plan" not in SD: SD["plan"] = plpy.prepare("SELECT fname FROM users WHERE lname = $1", [ "text" ]) rv = plpy.execute(SD["plan"], [ a ]) if len(rv): return rv[0]["fname"] return None ' LANGUAGE plpythonu; SELECT valid_type('rick'); /* check catching specific types of exceptions */ CREATE TABLE specific ( i integer PRIMARY KEY ); CREATE FUNCTION specific_exception(i integer) RETURNS void AS $$ from plpy import spiexceptions try: plpy.execute("insert into specific values (%s)" % (i or "NULL")); except spiexceptions.NotNullViolation, e: plpy.notice("Violated the NOT NULL constraint, sqlstate %s" % e.sqlstate) except spiexceptions.UniqueViolation, e: plpy.notice("Violated the UNIQUE constraint, sqlstate %s" % e.sqlstate) $$ LANGUAGE plpythonu; SELECT specific_exception(2); SELECT specific_exception(NULL); SELECT specific_exception(2); /* manually starting subtransactions - a bad idea */ CREATE FUNCTION manual_subxact() RETURNS void AS $$ plpy.execute("savepoint save") plpy.execute("create table foo(x integer)") plpy.execute("rollback to save") $$ LANGUAGE plpythonu; SELECT manual_subxact(); /* same for prepared plans */ CREATE FUNCTION manual_subxact_prepared() RETURNS void AS $$ save = plpy.prepare("savepoint save") rollback = plpy.prepare("rollback to save") plpy.execute(save) plpy.execute("create table foo(x integer)") plpy.execute(rollback) $$ LANGUAGE plpythonu; SELECT manual_subxact_prepared();