Bug #34165 mysql can't change a record that exists
Submitted: 30 Jan 2008 15:09 Modified: 7 Sep 2008 9:08
Reporter: Cyril SCETBON Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S2 (Serious)
Version:5.1.22-beta OS:Linux (debian etch)
Assigned to: CPU Architecture:Any

[30 Jan 2008 15:09] Cyril SCETBON 
Description:
when trying to update/delete a record from a disk table mysql complains that it can't find the record

How to repeat:
mysql> select count(*) from spp_disk01 where ise='ID-YYY-100-A5hE78RglF0OKLfgvRSD8NKwE02Z2tp2poRFcqkri7Y';
+----------+
| count(*) |
+----------+
|        1 | 
+----------+
1 row in set (0.02 sec)

mysql> delete from spp_disk01 where ise='ID-YYY-100-A5hE78RglF0OKLfgvRSD8NKwE02Z2tp2poRFcqkri7Y';
ERROR 1032 (HY000): Can't find record in 'spp_disk01'

CREATE TABLE `spp_disk01` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `ise` varchar(54) NOT NULL,
  `vc01` varchar(400) NOT NULL DEFAULT '',
  `vc02` varchar(1200) NOT NULL DEFAULT '',
  `ch03` char(10) NOT NULL DEFAULT '',
  `vc04` varchar(11) NOT NULL DEFAULT '-1',
  `vc05` varchar(11) NOT NULL DEFAULT '-1',
  `ch06` char(10) NOT NULL DEFAULT '',
  `ch07` char(10) NOT NULL DEFAULT '',
  `ch08` char(1) NOT NULL DEFAULT '',
  `ch09` char(3) NOT NULL DEFAULT '',
  `ch10` char(10) NOT NULL DEFAULT '',
  `in11` int(11) NOT NULL DEFAULT '-1',
  `in12` int(11) NOT NULL DEFAULT '-1',
  `vc13` varchar(255) NOT NULL DEFAULT '',
  `vc14` varchar(255) NOT NULL DEFAULT '',
  `ts15` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  `ts16` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
  `tx17` text CHARACTER SET utf8,
  `tx18` text CHARACTER SET utf8,
  `tx19` text CHARACTER SET utf8,
  `ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `ise` (`ise`)
) /*!50100 TABLESPACE ts_1 STORAGE DISK */ ENGINE=ndbcluster DEFAULT CHARSET=latin1
[30 Jan 2008 16:12] Jonas Oreland 
Hi,

Can you upload some sample data (and specify you config)
So we can reproduce this ?

/Jonas
[2 Feb 2008 9:32] Jonas Oreland 
is that sufficient to reproduce ?
[3 Feb 2008 20:58] Jonas Oreland 
Hi,

I tried your table and your example data, both with 5.1.22
  and upcoming 5.1.24 without being able to reproduce the problem.

I suggest that you either upload more data, 
  or wait for 5.1.24 and try with that

/Jonas
[4 Mar 2008 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[17 Mar 2008 12:54] Susanne Ebrecht 
Setting back to need Feedback because of waiting for informations with testing of newer version.
[17 Apr 2008 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 Apr 2008 10:39] Susanne Ebrecht 
Cyril,

we still need to know if you will still have this issue by using our newest version: MySQL 5.1.24.
[30 Apr 2008 12:51] Cyril SCETBON 
Acutally we cannot test this version on our production.
[7 Aug 2008 9:08] Susanne Ebrecht 
Take your time ... I will set this back to "need feedback" and when you can update and test then please let us know.
[7 Sep 2008 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".