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