Hello,
PostgreSQL allow only catch exception (elevel ERROR). SQL/PSM requires that
warnings are catchable too. Simply solution's is adding one callback to
error's processing of errors on level WARNING.
typedef struct WarningHandlerCallback
{
bool(*callback) (void *arg,
On Sun, 2007-01-07 at 09:59 +0100, Pavel Stehule wrote:
PostgreSQL allow only catch exception (elevel ERROR). SQL/PSM requires that
warnings are catchable too. Simply solution's is adding one callback to
error's processing of errors on level WARNING.
Exceptions are run within their own
On Sun, 2007-01-07 at 09:59 +0100, Pavel Stehule wrote:
PostgreSQL allow only catch exception (elevel ERROR). SQL/PSM requires
that
warnings are catchable too. Simply solution's is adding one callback to
error's processing of errors on level WARNING.
Exceptions are run within their own
On Sun, 2007-01-07 at 11:20 +0100, Pavel Stehule wrote:
On Sun, 2007-01-07 at 09:59 +0100, Pavel Stehule wrote:
PostgreSQL allow only catch exception (elevel ERROR). SQL/PSM requires
that
warnings are catchable too. Simply solution's is adding one callback to
error's processing of
Does the PSM warning error handler run in the same transaction or a
separate subtransaction? Can transaction execution continue afterwards?
It's depend. Continue and exit warning handlers run in the same
transaction,
undo handler has separate subtransaction. It works well. For
Pavel Stehule [EMAIL PROTECTED] writes:
PostgreSQL allow only catch exception (elevel ERROR). SQL/PSM requires that
warnings are catchable too.
What in the world does it mean to catch a warning? If your intention
is to process arbitrary user-defined code while inside the error
subsystem, I
What is problem? ANSI SQL has different model of handling exception than
postgresql. It doesn't distinguishes between warnings and exception. Simply
some sqlstate clases are reservated for warnings and other's for exception.
But all sqlstate's (without '0') can be handled via any CONTINUE,
Pavel Stehule [EMAIL PROTECTED] writes:
What is problem? ANSI SQL has different model of handling exception than
postgresql. It doesn't distinguishes between warnings and exception. Simply
some sqlstate clases are reservated for warnings and other's for exception.
But all sqlstate's
Pavel Stehule [EMAIL PROTECTED] writes:
What is problem? ANSI SQL has different model of handling exception than
postgresql. It doesn't distinguishes between warnings and exception.
Simply
some sqlstate clases are reservated for warnings and other's for
exception.
But all sqlstate's
