Use the clustered index and not the one selected by the optimizer in the plan,
when building a previous version of the row. This bug is triggered when running queries via InnoDB's internal SQL parser; when InnoDB's optimizer selects a secondary index for the plan.
Showing
Please register or sign in to comment