Description:
deleting non exiting row inside transaction breaks transaction

How to repeat:
look at CSC 25934 for the test case

Suggested fix:
n/a

Here is the simple test case:

-- The problem is with TEXT field. If we remove TEXT field everything works ok
DROP TABLE `t1`;
CREATE TABLE `t1` (
  `f1` int(11) NOT NULL DEFAULT -1,
  `f11` text,
  UNIQUE KEY `i1` (`f1`)
) ENGINE=ndbcluster DEFAULT CHARSET=utf8;

INSERT INTO `t1` VALUES (123,NULL);

DROP TABLE `t2`;
CREATE TABLE `t2` (
  `f1` int(11) NOT NULL DEFAULT -1,
  UNIQUE KEY `i2` (`f1`)
) ENGINE=ndbcluster DEFAULT CHARSET=utf8;

BEGIN; delete from t1 where f1=123; delete from t2 where f1=5; COMMIT;

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/46918

ChangeSet@1.2598, 2008-05-21 17:39:51+01:00, frazer@forth.ndb.mysql.com +5 -0
  Bug#36756 IgnoreError Delete of nonexisting tuple aborts
  
  Problem was that once a transaction handled Blobs, AbortOption was treated differently.

great patch,
i love the testing

Pushed into 5.1.23-ndb-6.4.0

Pushed into 5.1.24-ndb-6.3.15

Pushed into 5.1.24-ndb-6.2.16

Documented in the 5.1.24-ndb-6.3.15 and 5.1.24-ndb-6.2.16 changelogs as follows:

        Attempting to delete a non-existent row from a table containing a TEXT
        or BLOB column within a transaction caused the transaction to fail.

Closed.

Pushed into 6.0.6-alpha  (revid:sp1r-frazer@forth.ndb.mysql.com-20080521163951-23571)
(version source revid:jonas@mysql.com-20080808094047-4e1yiarqa2t3opg3) (pib:5)