Comment 11 for bug 978432
Revision history for this message
| Daniel Nichter (daniel-nichter) wrote | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Turns out the problem doesn't happen in 2.0 because in that series the tool still used SHOW TABLE STATUS for the row estimate, thereby not returning a MySQL-chosen index. But when --where is used, then it uses EXPLAIN and return's MySQL chosen index.