/ Ticket Change Details

Artifact ID: 19ffc8588b412a36627e25b38312f0cbf707bc68f88837abb8ae378f79eeabf2
Ticket: fb8c538a8f57ae2a69540a293141dcc9dfb832b5
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

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

  2. Change login to "drh"
  3. Change mimetype to "text/x-fossil-wiki"
  4. Change priority to "Low"
  5. Change resolution to "Open"
  6. Change subsystem to "Unknown"