sqlite

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	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	e0568d6fb8	Fix an obscure problem in range estimation with STAT4. FossilOrigin-Name: 1f16c9a76bc48331799f33b30d143c632fe0e7db	2016-12-09 00:15:17 +00:00
drh	fa385edff3	A new approach to very large sqlite3_mprintf() strings: Back out the [d655a665] check-in and instead make the size fields in StrAccum unsigned. Strings generated by sqlite3_mprintf() can now be as large as 2^31-1 bytes. FossilOrigin-Name: 7adb789f45698e5569b840d23f3f9488db3ed109	2016-01-04 12:07:27 +00:00
dan	3df3059252	Extra tests for commit [0f250957]. FossilOrigin-Name: 5aa522dcb9bfa18d49683f7cc889516984e2bcd2	2015-03-13 08:31:54 +00:00
dan	18bf807689	Allow the query planner to evaluate deterministic scalar SQL functions used in WHERE constraints if all arguments are SQL literals in order to compare the results with sqlite_stat4 sample data. FossilOrigin-Name: b7f1fc26d24012e1e7c7f6b3cc0b84ad2b02b8ad	2015-03-11 20:06:40 +00:00