Bug #39259 Table entry field that should be NULL behaves improperly sometimes
Submitted: 4 Sep 2008 21:44 Modified: 4 Oct 2008 22:26
Reporter: David Zafman Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:Ver 14.12 Distrib 5.0.22 OS:Linux (CentOS release 5)
Assigned to: CPU Architecture:Any
Tags: DEFAULT, insert, null

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:

[4 Sep 2008 21:45] David Zafman
Session which shows database inconsistency

Attachment: bug39259.txt (text/plain), 7.54 KiB.