5 Commits

Author	SHA1	Message	Date
drh	348e002ec9	One of the optimizations of check-in [de9c86c9e4cdb34f] does not work for ... terms originating in the ON/USING clause, as demonstrated by [forum:/forumpost/6cf3bb457c3f4685|forum post 6cf3bb457c3f4685]. This check-in disables that optimization for ON/USING terms. Also improve the TreeView display for the resulting "true"/"false" nodes to show that they originate from the ON/USING clause. Add a testcase() to the other optimization to show that it can still be used for ON/USING terms. FossilOrigin-Name: 1f6796044008e6f3a61bcf390c0c7eb31947e971f0edada74e7a3a211f8ae76a	2021-07-22 16:07:01 +00:00
dan	677e62aacd	Fix a problem with handling expressions like "(col IS NULL AND <expr1>) OR col == NULL" in WHERE clauses. ... FossilOrigin-Name: 40852ca8e215e51f63652a67817361b835b6fbbff7f66af50089af91007505f1	2021-04-10 14:49:45 +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	15de3ce9ab	Fix a segfault that could occur when optimizing a NOT NULL constraint against an IPK column of a sub-query. ... FossilOrigin-Name: e4d1970ef17b2330f78c750d71d625c2997f79ed1445d0351ec32b482485a954	2021-02-26 21:39:34 +00:00
dan	8ddf686267	Attempt to optimize "x IS NULL" and "x IS NOT NULL" expressions when x is a column with a NOT NULL constraint. ... FossilOrigin-Name: 5ecd842555009ce27ee6390325ac5c2504143474b12b730933f0833b3dad788a	2021-02-26 20:14:32 +00:00