Incorrect sorting when a column uses BINARY collation in the ORDER BY, but is constrained by an == with a different collation in the WHERE clause
|User & Date:||drh 2020-02-12 11:18:29|
- Change icomment to:
This problem appears to have been introduced by the Next Generation Query Planner change of version 3.8.0, and specifically check-in [0fe31f60cadc5fe5] (2013-06-21). This problem was found in the wild and was brought to the attention of the developers via a private email message.
- Change login to "drh"
- Change mimetype to "text/x-fossil-wiki"
- Change priority to "Low"
- Change resolution to "Open"
- Change subsystem to "Unknown"