|Title:||Over-aggressive optimization of ORDER BY using a virtual table with IN operator|
|Last Modified:||2013-04-18 02:55:56|
|Version Found In:||184.108.40.206|
drh added on 2013-04-17 23:38:35:
When a query of a virtual table uses an IN operator in the WHERE clause as its index and it has an ORDER BY clause, it is possible that the ORDER BY clause might be optimized away and the sort omitted when in fact the sort is required for the correct answer.
This problem appears to have been introduced by check-in [3d65c70343] on 2012-12-14 for version 3.7.16.