From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Thomas Berg <tomfuture@hotmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Cascade updates wait until the end of the transaction?
Date: Mon, 15 Nov 2004 22:52:22 -0800 (PST)
Message-ID: <20041115224713.K53414@megazone.bigpanda.com> (raw)
In-Reply-To: <cn19tg$1gq5$2@news.hub.org>
References: <cn19tg$1gq5$2@news.hub.org>
On Fri, 12 Nov 2004, Thomas Berg wrote:
> Within a function (and therefore within a transaction), if I UPDATE the
> primary key of a table, the old value remains visible in the child table
> through the end of the function. Is this
8.0 runs immediate triggers after each statement of a function and also
forces referential actions to be treated as immediate and as such should
change the behavior mentioned.
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sszabo@megazone.bigpanda.com, tomfuture@hotmail.com
Subject: Re: Cascade updates wait until the end of the transaction?
In-Reply-To: <20041115224713.K53414@megazone.bigpanda.com>
* 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