Bug #38015 | Bad result: inconsistent treatment of comparisons between data types in subquery | ||
---|---|---|---|
Submitted: | 10 Jul 2008 13:11 | Modified: | 14 Sep 2009 10:50 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 6.0,5.4 | OS: | Any |
Assigned to: | Øystein Grøvlen | CPU Architecture: | Any |
Tags: | regression, subquery |
[10 Jul 2008 13:11]
Philip Stoev
[10 Jul 2008 14:32]
MySQL Verification Team
Thank you for the bug report. Repeatable on 6.0.4/6.0.6. Not repeatable on 5.0/5.1/6.0.2.
[14 Jul 2009 22:21]
Patrick Crews
My testing showed matching result sets between 5.1 and azalea for queries 2 and 3. Query 1 produced differing result sets that were not affected by azalea's optimizer_switch, engine_condition_pushdown, and optimizer_use_mrr values.
[14 Sep 2009 10:50]
Øystein Grøvlen
I am not able to repeat this on the current head of mysql-next. All queries return 4 rows.
[14 Sep 2009 15:01]
Philip Stoev
Agree. Bug is no longer repeatable.