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

17 Commits

Author SHA1 Message Date
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
drh
5198ff5767 Do not generate subroutines for non-static SELECT and EXISTS expressions. 
Fix up some test cases to account for the minor changes in EXPLAIN QUERY PLAN
output.

FossilOrigin-Name: 06de44ec9e173992ca9afb89dd2b4e40d2a7e35512c7959603cdceb606f5dfbd
 2018-12-24 12:09:47 +00:00
drh
6d6decb8d9 Only choose to scan an IN operator rather than use an index if we have 
real STAT1 data to suggest it is advantageous.

FossilOrigin-Name: 30e874661dcc1a2ecb40df2ef74582151d85bb36c754a38548829a3b6285f18d
 2018-06-08 21:21:01 +00:00
drh
b3f0276b9e Fix test cases so that they work with the new EXPLAIN QUERY PLAN output 
format.  Only some of the cases have been fixed.  This is an incremental
check-in.

FossilOrigin-Name: 5f0e803e33aa557865d5fc830d9202d628de9a94c9757058ca48f1a560702cd3
 2018-05-02 18:00:17 +00:00
drh
083aefc732 Do vector comparison size checking early - at name resolution time - to 
forestall future problems.

FossilOrigin-Name: ae127bcc0a5827786853f47b229021435d6098d7
 2016-09-05 12:12:56 +00:00
drh
b29e60c448 Catch vector size mismatch problems during name resolution to avoid later 
problems.

FossilOrigin-Name: 56562a0346170cf7b72445976864b058437a8ac3
 2016-09-05 12:02:34 +00:00
dan
5c3340bd47 Fix a crash that could occur under certain circumstances if the vectors on either side of a comparison operator were of a different size. 
FossilOrigin-Name: 42670935aba152ba774c2a8bdcbe72b943309d68
 2016-09-05 09:44:45 +00:00
drh
e835bc1285 Simplify the row value misuse error message. 
FossilOrigin-Name: 838c50a5bf46fd0340839d577fa28ba02b4f2034
 2016-08-23 19:02:55 +00:00
dan
f358009a93 Fix a segfault that could occur if a query that used a vector comparison contained certain types of syntax errors. 
FossilOrigin-Name: 203f07c5e140e74cf91d0c1e20135c21236f0fc1
 2016-08-20 15:01:24 +00:00
dan
17994e3bca Fix some problems with handling "no such collation sequence" errors. 
FossilOrigin-Name: 8278be06fa69e3266866220bdaf5be45a5fcfa23
 2016-08-11 12:01:52 +00:00
dan
1d9bc9b7a0 Fix the EXPLAIN QUERY PLAN output for row value range constaints that use an index. 
FossilOrigin-Name: bb60651163553c5e46bf7b2805490570cea647b8
 2016-08-08 18:42:08 +00:00
dan
3d1fb1dd75 Fix a problem with estimating the number of rows visited by a query that uses a multi-column IN(SELECT...) constraint. 
FossilOrigin-Name: 3c2f908f5b7312570cfa74afcf4252a857cb5237
 2016-08-03 18:00:49 +00:00
dan
2c628ea9d9 Fix another problem involving vector range constraints and mixed ASC/DESC indexes. 
FossilOrigin-Name: 1559f4c43473e107f7196eea3ee91c53ede22999
 2016-08-03 16:39:04 +00:00
dan
d66e5794d1 Fix stat4-based cost estimates for vector range constraints. 
FossilOrigin-Name: 18af74abc8ceae47ab9fbee3e3e5bb37db8fcba5
 2016-08-03 16:14:33 +00:00
dan
51d82d1d24 Add tests and fixes for vector operations that use sub-queries with different combinations of LIMIT, OFFSET and ORDER BY clauses. 
FossilOrigin-Name: 092b1c5ff53c9f3cfed079c46e3353d93f99303e
 2016-08-02 18:50:15 +00:00
dan
d05a7144cd Fix a problem with vector range constraints and mixed ASC/DESC indexes. 
FossilOrigin-Name: e2ad30c8b5366fd8e50f36c62345ed03ec613c47
 2016-08-02 17:07:51 +00:00
dan
7b35a77b1a Fix further issues with multi-column IN(...) operators. Also some error handling cases surrounding row values. 
FossilOrigin-Name: cc3f6542bec99b00d2698889bcea2aa0b587efa0
 2016-07-28 19:47:15 +00:00