4 Commits

Author	SHA1	Message	Date
dan	210ec4c855	Fix a virtual table problem that can occur when the vtab is on the RHS of a ... LEFT JOIN and there is a MATCH constraint in the ON clause, or when the vtab is in a sub-query that is the RHS of a LEFT JOIN and there is a MATCH constraint in the WHERE clause of the sub-query. FossilOrigin-Name: 87b381663398f029f52cb5598aadd069b03034b6f833ce80ba762b406075a44e	2017-06-27 16:39:01 +00:00
drh	a23bc8a345	From test scripts, remove stray "breakpoint" commands and blank lines ... at the ends of files. FossilOrigin-Name: a6b35273239669189f33402144f58328b133d182	2016-02-05 16:46:09 +00:00
dan	69014393f8	Instead of having the planner ignore plans with unusable MATCH constraints, have FTS assign extremely high costs to such plans in order to discourage the planner from using them. ... FossilOrigin-Name: 24f84b38131866f7b435ffe641bb2f6991a70db2	2014-01-04 14:42:14 +00:00
dan	42899543f8	Have the planner detect cases where a MATCH constraint is applied to a virtual table, and ignore any plans that do not allow the virtual table implementation to implement the MATCH filtering. ... FossilOrigin-Name: 19f3208b26597625728d1ef716d4e44407cf96ac	2014-01-04 14:16:06 +00:00