From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problems handling errors in PL/pgSQL
Date: Mon, 23 Apr 2001 19:57:23 -0400
Message-ID: <24242.988070243@sss.pgh.pa.us> (raw)
In-Reply-To: <web-43127@davinci.ethosmedia.com>
References: <web-43127@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> writes:
> However, not all types of errors are so trapped. The most problematic
> un-trapped error is referential integrity: if an INSERT or UPDATE fails
> because of a referential integrity violation, the PL/pgSQL function will
> still see the statement as a success and not error out.
This would clearly be a bug, but I cannot replicate the problem:
regression=# SELECT fn_save_order_details (7703, '{34,29,40}','{TRUE, TRUE, FALSE}');
ERROR: <unnamed> referential integrity violation - key referenced from order_details not found in orders
regression=#
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Problems handling errors in PL/pgSQL
In-Reply-To: <24242.988070243@sss.pgh.pa.us>
References: <web-43127@davinci.ethosmedia.com> <24242.988070243@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox