Hi all.

I am having a wierd problem with triggers and stored procedures. This is causing database to be in inconsistent state.

1. I have added a trigger to be called AFTER insert on a table (t1), which adds a row into another table(say t2). 2. Client connects to the table t1 and inserts desired row and closes connection normally. 3. If client is terminated in between, or more generally : If trigger operation is not completed before client closes the connection after inserting row in t1, database goes in inconsistent state : we have a row in table t1 but not the desired row in t2.

Should not it be atomic: add a row in table t1 and call trigger(which adds the row to t2), or do nothing.

Please let me know if you need more information to solve the problem.

Can anybody help me out?

Thanks and regards. Pushya