MySQL Bugs: #11133: WriteTuple returns 626, if previous op in trans is a delete

Bug #11133	WriteTuple returns 626, if previous op in trans is a delete
Submitted:	7 Jun 2005 11:04	Modified:	14 Jun 2005 3:19
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	4.1, 5.0, 5.1	OS:
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
start transaction
insert T1
delete T1
write T1 -> 626

How to repeat:
start transaction
insert T1
delete T1
write T1 -> 626

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/internals/25700

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/internals/25703

pushed in 4.1.13 and 5.0.8

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in change history for 4.1.13 and 5.0.8. Closed.

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/internals/26577

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/internals/27470