Bug #43617 Innodb returns wrong results with timestamp's range value in IN clause
Submitted: 13 Mar 2009 5:01 Modified: 18 Dec 2009 12:14
Reporter: Nidhi Shrotriya Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S3 (Non-critical)
Version:6.0.11-bzr OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: index_condition_pushdown, optimizer_switch

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:

[13 Mar 2009 5:02] Nidhi Shrotriya
Test Case

Attachment: timestamp_bug_innodb.test (application/octet-stream, text), 3.78 KiB.