On Thu, Oct 23, 2003 at 08:16:27AM +0100, Peter Childs wrote:
>
>
> On Wed, 22 Oct 2003, scott.marlowe wrote:
>
> > On Wed, 22 Oct 2003, Peter Childs wrote:
> >
> > > Is it possible to deferr a trigger until commit, Or to have the
> > > trigger not occur if the transaction is rolled back? Like transaction.
>
> Background, we are trying to get the database to tell clients when
> records get updated, deleted or inserted so that they can update there
> on-screen displays without having to query the database every couple of
> seconds which would put an unnessary strain on the database. Hence
> producing quicker respose times.
You should probably be using an AFTER trigger ... when those get
executed, the transaction is ready to commit and will not abort (barring
any major problems, like your server go nuts or something).
But why don't you use some notifications and set up appropiate listeners
on the OSDs? See the NOTIFY/LISTEN reference pages ... these also get
delivered during transaction commit.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"In fact, the basic problem with Perl 5's subroutines is that they're not
crufty enough, so the cruft leaks out into user-defined code instead, by
the Conservation of Cruft Principle." (Larry Wall, Apocalypse 6)
