]> git.ipfire.org Git - thirdparty/sqlite.git/commit
When determining whether an == or IS constraint in a WHERE clause makes an ORDER...
authordan <dan@noemail.net>
Wed, 12 Feb 2020 11:57:35 +0000 (11:57 +0000)
committerdan <dan@noemail.net>
Wed, 12 Feb 2020 11:57:35 +0000 (11:57 +0000)
commit41aa442cf4fd66cafbc37f3a1718aeb4c498a96f
treeb1b97c4524faca0645e485793571397e8ffa66b6
parentdf9b5cab9354fa7863037c647131c10ad063f7ee
When determining whether an == or IS constraint in a WHERE clause makes an ORDER BY term redundant, consider the collation sequence used by the == or IS comparison, not the collation sequence of the comparison expression itself. Possible fix for [fb8c538a8f].

FossilOrigin-Name: 16aed5d0c63dcdc2054dbb8a4b6b992476640433bf81e19301e6db5a3fc82633
manifest
manifest.uuid
src/where.c
test/orderby5.test