Re: Why are triggers semi-deferred? - Mailing list pgsql-hackers

From Philip Warner
Subject Re: Why are triggers semi-deferred?
Date
Msg-id 5.1.0.14.0.20030713120109.03a024d0@mail.rhyme.com.au
Whole thread Raw
In response to Re: Why are triggers semi-deferred?  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
At 10:38 AM 12/07/2003 -0700, Stephan Szabo wrote:
>  deferred after trigger row 1
>  deferred after trigger #2 row a
>  deferred after trigger row 2
>  deferred after trigger #2 row b

I'd vote for this; ie. make them execute in the same order they would 
execute if they were not deferred. Otherwise you open up all sorts of weird 
application errors if a trigger is deferred/not-deferred.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/



pgsql-hackers by date:

Previous
From: Kenji Sugita
Date:
Subject: vacuumdb can't be canceled
Next
From: Jan Wieck
Date:
Subject: Re: php with postgres