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.
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.