Skip site navigation (1) Skip section navigation (2)

Re: BUG #1781: result of cascading triggers not available

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Andrew Smith <andrew(at)asmith(dot)id(dot)au>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1781: result of cascading triggers not available
Date: 2005-07-23 16:59:22
Message-ID: 20050723094554.Y84629@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sat, 23 Jul 2005, Andrew Smith wrote:

> The following bug has been logged online:
>
> Bug reference:      1781
> Logged by:          Andrew Smith
> Email address:      andrew(at)asmith(dot)id(dot)au
> PostgreSQL version: 7.4.6
> Operating system:   Debian GNU/Linux 3.1
> Description:        result of cascading triggers not available until
> function exits.

I don't think the 8.0 changes are a candidate for patching to earlier
versions, so I think the only option is to upgrade if you want the newer
behavior.

In response to

pgsql-bugs by date

Next:From: MohamedDate: 2005-07-23 17:09:14
Subject: BUG #1782: unexpected EOF on client connection
Previous:From: Andrew SmithDate: 2005-07-23 09:59:48
Subject: BUG #1781: result of cascading triggers not available until function exits.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group