MySQL Bugs: #57466: Transaction Isolation problem via Duplicate Keys with impossible error data.

Bug #57466	Transaction Isolation problem via Duplicate Keys with impossible error data.
Submitted:	14 Oct 2010 18:50	Modified:	22 Oct 2010 23:37
Reporter:	Daniel Smythe	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	6.3.26 +	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any
Tags:	cluster, duplicate keys, transaction isolation

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Simpler test case, with lock table/row in transaction, table schema, test php script, and sample combined output of 2 events.

Attachment: bug57466.txt (text/plain), 6.05 KiB.

"my version"

Attachment: bug57466.tgz (application/x-compressed-tar, text), 695 bytes.