This website requires JavaScript.
Explore
Help
Sign In
mirrors
/
sqlite
Watch
1
Star
0
Fork
0
You've already forked sqlite
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
sqlite
/
manifest.uuid
1 line
64 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Fix for the problem identified in [forum:/forumpost/0cd8e058bf|forum post 0cd8e058bf]: When evaluating an multi-index OR, do not push down auxiliary WHERE clause terms that involve subqueries into the OR-subqueries. Otherwise, the covering-index optimizer might convert table-references into index-references for the particular OR index that is active for the branch in which the subquery subroutine is coded, and those index-references will not work if the subquery subroutine is invoked from a different OR branch that uses a different index. FossilOrigin-Name: 61a1c6dbd089979cbeb8b0c0c5ee1ab1abcb466be1d21a3a851be73c27e67a6c
2022-03-03 15:59:22 +00:00
61a1c6dbd089979cbeb8b0c0c5ee1ab1abcb466be1d21a3a851be73c27e67a6c
Reference in New Issue
Copy Permalink