Re: Weird problem : Trigger not executed in background.

Hi,

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

What storage engine is used for tables t1 and t2?

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

Yes, for InnoDB (or for any storage engines that support transactions, at 
least).

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

I need a complete test case and version of MySQL server used.

Best regards,
-- 
Valeriy Kravchuk, Support Engineer
MySQL AB, Kiev, Ukraine, www.mysql.com


-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]