Subject | Re: [IBO] Lock Conflict Problem |
---|---|
Author | Lester Caine |
Post date | 2005-06-28T06:02:46Z |
Jason Wharton wrote:
I'd pulled an all nighter to finish a major update and was not thinking
straight :(
Visibility of the results was more what I was thinking about, but of
cause the 'instigator' can see that within the transaction.
I tend to keep things tight so that transactions are not held over
longer than necessary using things like cached updates in IBO.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
> Triggers always fire in conjunction with the insert, update or delete and toForget what I said ;)
> my knowledge there are no triggers that fire upon commit. However, the
> changes invoked by the triggers are subject to the transaction.
I'd pulled an all nighter to finish a major update and was not thinking
straight :(
Visibility of the results was more what I was thinking about, but of
cause the 'instigator' can see that within the transaction.
I tend to keep things tight so that transactions are not held over
longer than necessary using things like cached updates in IBO.
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services