MySQL Bugs: #43891: NULL bit offset not taken into account

Bug #43891	NULL bit offset not taken into account
Submitted:	26 Mar 2009 17:16	Modified:	30 Mar 2009 17:17
Reporter:	Max Mether	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: NDB API	Severity:	S3 (Non-critical)
Version:	6.2	OS:	Any
Assigned to:	Frazer Clement	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

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

Proposed patch, including testcase and some minor compile warning cleanup

Attachment: nullbit.patch (text/x-patch), 5.50 KiB.

Improved patch with invocation added to daily-basic

Attachment: nullbit.patch (text/x-patch), 5.91 KiB.