mirrors/sqlite
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
27,750 Commits 1,487 Branches 166 Tags 416 MiB
4c11a5251a
Commit Graph

12 Commits

Author SHA1 Message Date
drh
80e936aef0 Do a better job of detecting when a WHERE clause term might be useful to 
an expression index.  Fix for performance regression reported by
[forum:/forumpost/e65800d8cb|forum thread e65800d8cb].

FossilOrigin-Name: 44200596aa943963bc6ca98b5d4fd5b9235d1109d8dfc1a75eeae353b4239142
 2023-02-10 21:53:33 +00:00
drh
6a9595a76b Avoid adding superfluous virtual WHERE clause terms that might arise due 
to the constant propagation optimization.

FossilOrigin-Name: cf63abbe559d04f993f99a37d41ba4a97c0261094f1d4cc05cfa23b1e11731f5
 2021-05-14 15:37:00 +00:00
drh
8210233c7b Revise tests cases to align with the new EXPLAIN QUERY PLAN output. 
FossilOrigin-Name: 50fbd532602d2c316813046ed6be8be2991c281eb5f295c4c28520a0de73862c
 2021-03-20 15:11:29 +00:00
dan
de9ed6293d Allow sub-queries that use UNION ALL to be flattened, even if the parent query is a join. Still some problems on this branch. 
FossilOrigin-Name: 00e4bf74d3dfb87666a2266905f7d1a2afc6eb088d22cfd4f38f048733d6b936
 2020-12-16 20:00:46 +00:00
drh
742efb6749 New test case for ticket [1dcb4d44964846ad]. 
FossilOrigin-Name: 9e9f1e96c9aac60fcbbcda6923e01e350ca4dd88acefb9d400979419ba4e1e4d
 2020-04-24 17:55:52 +00:00
drh
fdfd45aef3 Fix problems in the constant propagation optimization that were introduced 
by check-in [1c3e5c20a9e6f501].  Fix for ticket [1dcb4d44964846ad]

FossilOrigin-Name: c9a8defcef35a1fee6bcbb88252a2d0076dabe8381b0128b2257b5b5cc494e0f
 2020-02-13 22:12:35 +00:00
drh
c9301e6e7c Fix the constant propagation optimization so that it does not try to 
propagate constant expressions that have affinity.  Ticket [82ac75ba0093e5dc]

FossilOrigin-Name: 6db1c3498f6bfa01bb460e62b802b63ec4bf43577a17a94e1e2fa0ecc1e64960
 2020-01-08 01:43:47 +00:00
drh
8e5bfedd22 In the WHERE-constraint propagation optimization, if there are duplicate 
constraint, make sure only one of them propagates.  Proposed fix for
ticket [cf5ed20fc8621b165].

FossilOrigin-Name: 5d5b596f152bb2781011a05f75f9e200774d4f69d648ef68de577b4ace973e07
 2018-10-25 14:15:37 +00:00
drh
d98f53249c When a column must be a constant due to WHERE clause and the value of that 
column is being coded as a constant, make sure the affinity is correct.

FossilOrigin-Name: 7404ea83168e6c739ebe8fc5d65bbf0265432ccb35b3418bb0381d74362f7527
 2018-08-09 18:36:54 +00:00
drh
7de7602eb7 Add a test case demonstrating the collation problem with constant propagation. 
FossilOrigin-Name: 50add839fd95665bd67a6ae5de8346fd09e83904bbcbad26fad280dff86d9e93
 2018-07-26 23:54:19 +00:00
drh
24e1116e0f Generalize the constant propagation optimization so that it applies on every 
WHERE close, not just those that contain a subquery.  This then demonstrates
that the current implementation is inadequate since it does not take into
account collating sequences.

FossilOrigin-Name: 57eb2abd5b270d65be5e0f138f0d46899fa6091df3ba20b0ea7ef04244a15d48
 2018-07-26 23:47:11 +00:00
drh
660ee55663 Initial implementation of the WHERE-clause constant propagation optimization. 
FossilOrigin-Name: 2fb82ad8ebb6434438c0d235b1239444fb08c8711cea2c5a9ed955fedd0acdec
 2018-07-26 21:16:53 +00:00