Triggers always fire in conjunction with the insert, update or delete and to
my knowledge there are no triggers that fire upon commit. However, the
changes invoked by the triggers are subject to the transaction.

Jason Wharton
www.ibobjects.com

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Lester Caine
> Sent: Monday, June 27, 2005 12:26 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] Lock Conflict Problem
>
>
> Calin Pirtea wrote:
>
> >>From: Lester Caine
> >
> >>Again, the trick is to keep to a minimum the information that is
> >>modified. The triggers are not fired until a commit is made, so
> >>everything should be stable, and nothing should lock because
> >>the commit
> >>happens quickly. The problem comes when you start trying to scan
> >>multiple records which other users may also be accessing ...
> >
> > Lester, I think you meant the trigger is not fired until
> the record is
> > inserted or updated, and if AutoCommit is on then the
> commit will happen as soon
> > as the insert/update succeeds.
>
> Yes and No - If autocommit is on, then Yes the insert and commit will
> happen at the same time, but if it is off - as it should be -
> then the
> trigger will not fire until the current transaction is commited.
>
> --
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services