]> git.ipfire.org Git - thirdparty/sqlite.git/commit
When multiple constraints need to be evaluated for a row, do any constraints
authordrh <drh@noemail.net>
Mon, 10 Jul 2017 17:00:31 +0000 (17:00 +0000)
committerdrh <drh@noemail.net>
Mon, 10 Jul 2017 17:00:31 +0000 (17:00 +0000)
commit90e39ec34904055d7bcd967d01b4d2dd31d6bd58
treefbfe85de32461a31a8806d7c7fb116d37374d7c6
parent9f6e14c1ef5e62a1972b042c6f252bbd2a7ecb18
parent66a0bf31cc812a7b046f6280c6eea757f8298e19
When multiple constraints need to be evaluated for a row, do any constraints
that involve correlated subqueries last.  Hence, the priority is index-covered
constraints first, correlated subquery constraints last, and all others in
the middle.  This is a
follow-on and improvement to the push-down optimization of check-in [d7bb79ed].

FossilOrigin-Name: c4cb90487f34937605732c3959891075e2aabfb0bd05e55c44565d65867093ea
manifest
manifest.uuid