"Lester Caine" wrote:

> 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 ...

From there words I understand that
if there is an update on other tables
there you have to put a control/handler for possible conflict occurence.

Thanks a lot for sharing your experience with us Lester.

Kind Regards,


Metin Gonen



---
avast! Antivirus: Giden mesaj temiz.
Virus Veritabani (VPS): 0525-5, 25.06.2005
Test zamani: 26.06.2005 17:59:59
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com