5 Commits

Author	SHA1	Message	Date
drh	8718f52624	Disable an overzealous optimization the omitted sorting on a join if the first ... table gave a unique result. The sort can only be omitted if all tables in the join are unique. Ticket #1358. (CVS 2589) FossilOrigin-Name: 4f07661279fb11a06b3ddffeda672f077c0d306a	2005-08-13 16:13:04 +00:00
drh	943af3cda1	Fix problems caused by over-agressive optimization of ORDER BY in joins. ... Lots more testing needed. (CVS 2571) FossilOrigin-Name: 1a4e526d46280970b43505a5c8a4090767c63043	2005-07-29 19:43:58 +00:00
drh	6c30be8e51	Optimizer now converts OR-connected WHERE-clause terms into an IN operator so ... that they can be used with indices. There are known problems with the ORDER BY optimization in this and in several prior check-ins. This check-in is not recommended for production use. (CVS 2569) FossilOrigin-Name: d23c8bf81e508722e92ff1b9c8bc98dc026a31f2	2005-07-29 15:10:17 +00:00
drh	ed37800693	The BETWEEN operator in a WHERE clause is now able to use indices. (CVS 2568) ... FossilOrigin-Name: cdf8c9584b945212e065e044df801c207aedb675	2005-07-28 23:12:08 +00:00
drh	a611040eea	Test cases and tuning of the new optimizer code. (CVS 2567) ... FossilOrigin-Name: 4b02703dec71aa78e5f8d8cab5b950966a4c6abc	2005-07-28 20:51:19 +00:00