Bug #29523 Transactions do not work - cross-session data corruption
Submitted: 3 Jul 2007 15:56 Modified: 14 Sep 2008 1:35
Reporter: Antony Curtis Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Federated storage engine Severity:S4 (Feature request)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any
Tags: disabled
Triage: Triaged: D5 (Feature request)

[3 Jul 2007 15:56] Antony Curtis
Description:
Performing COMMIT on within one session on a federated table causes all other sessions which use the same table to have their data committed as well.

How to repeat:

connection master1;
set autocommit=0;
INSERT INTO federated.t1 (id, name) VALUES (1, 'foo');
INSERT INTO federated.t1 (id, name) VALUES (2, 'bar');

connection master2;
set autocommit=0;
INSERT INTO federated.t1 (id, name) VALUES (3, 'wibble');

connection master1;
COMMIT;

connection master2;
ROLLBACK;

Select on table will reveal all three rows have been inserted.

Suggested fix:
Remove current federated 'transactions' implementation as it does not work at all.
[9 Jul 2007 23:43] Miguel Solorzano
Thank you for the bug report.
[18 Jul 2007 17:15] Miguel Solorzano
See bug: http://bugs.mysql.com/bug.php?id=29875
[14 Sep 2008 1:35] Antony Curtis
This bug is actually fixed in FederatedX