Bug #52283 | Innodb reports extra warnings when SELECT/WHERE is performed using invalid value | ||
---|---|---|---|
Submitted: | 22 Mar 2010 19:10 | Modified: | 23 Mar 2010 16:32 |
Reporter: | Nirbhay Choubey | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.1.46 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql-5.1-bugteam, regression |
[22 Mar 2010 19:10]
Nirbhay Choubey
[22 Mar 2010 20:18]
Sveta Smirnova
Thank you for the report. Verified as described.
[26 Mar 2010 18:03]
Mikhail Izioumtchenko
the execution plan indicates an optimizer bug as 'impossible WHERE' implies there's no need to go to the SE. In fact I'd expect it to reproduce similarly with a MyISAM table, could you try. Optimistically categorizing away from InnoDB.