Bug #52784 Non optimal execution plan when using "NULL-safe not equal" on partitioned table
Submitted: 13 Apr 2010 14:02 Modified: 13 Apr 2010 14:37
Reporter: Christian Sauer Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S3 (Non-critical)
Version:5.1.43, 5.6.99-m4 OS:Any
Assigned to: CPU Architecture:Any
Tags: NULL-safe NOT equal, partitions

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: