Bug #67972 again trigger bug occured
Submitted: 25 Dec 2012 9:12 Modified: 11 Dec 2014 6:16
Reporter: ws lee Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:mysql5.5.27-ndb7.2.8 OS:Any
Assigned to: CPU Architecture:Any
Tags: regression

[25 Dec 2012 9:12] ws lee 
Description:
creepy ndb 7.2 version, indeed!!!!!!!
unbelivable production relase version!!!!!

How to repeat:
mysql> CREATE TABLE `test` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `no` int(11) NOT NULL,
  `status` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=ndbcluster AUTO_INCREMENT=4 DEFAULT CHARSET=utf8;

mysql> delimiter //

mysql> CREATE TRIGGER trg_test BEFORE UPDATE ON test
FOR EACH ROW
BEGIN
   IF (old.no <> new.no) 
   THEN
       call dummy;
   END IF;
END
//
delimiter ;

mysql> delimiter ;

mysql> insert into test values (111,222,333);
Query OK, 1 row affected (0.00 sec)

mysql> select * from test;
+-----+-----+--------+
| id  | no  | status |
+-----+-----+--------+
| 111 | 222 |    333 |
+-----+-----+--------+
1 row in set (0.00 sec)

mysql> UPDATE test SET status = 515 WHERE id = 111;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> select * from test;
+-----+----+--------+
| id  | no | status |
+-----+----+--------+
| 111 |  0 |    515 |
+-----+----+--------+

see `no` cloumn.

the value is 0.

why???????????????????????????

Suggested fix:
it seems to related primary key.
[25 Dec 2012 9:13] ws lee 
this bug similar to http://bugs.mysql.com/bug.php?id=67451
[25 Dec 2012 9:17] ws lee 
currently bug fix very very slow.
i am afraid mysql cluster is the end.
[25 Dec 2012 19:41] Sveta Smirnova 
Thank you for the report.

Verified as described. Not repeatable with version 7.1
[7 May 2013 5:27] 李 源錫 
also, same bug exist in mysql5.5.30-ndb7.2.12.
[19 Jun 2013 1:43] 李 源錫 
also, same bug exist in mysql5.5.31-ndb7.2.13.

this critabl bug was reported last year.
already passed 7 month.

unbelivable.
unbelivable.
unbelivable.

why not patch about this bug?
[19 Jul 2013 1:11] Yoshiaki Yamasaki 
I couldn't reproduce the bug on 5.6.11-ndb-7.3.2-cluster. 

It seems like that the bug solved on 5.6.11-ndb-7.3.2-cluster.
[19 Jul 2013 6:33] 李 源錫 
I don't have any migrate plan from current 7.2 to 7.3
still, this bug exist in mysql cluster 7.2
[11 Dec 2014 6:16] MySQL Verification Team 
Marking this as duplicate of Bug #74751.