6 commits

Author	SHA1	Message	Date
sergefp@mysql.com	699291a8e6	BUG#14940 "MySQL choose wrong index", v.2 ... - Make the range-et-al optimizer produce E(#table records after table condition is applied), - Make the join optimizer use this value, - Add "filtered" column to EXPLAIN EXTENDED to show fraction of records left after table condition is applied - Adjust test results, add comments	2006-07-28 21:27:01 +04:00
sergefp@mysql.com	1f21ac3cd3	Fix for BUG#8579 (failing test case): Allow small differences in #rows estimate in test results	2005-02-22 18:30:44 +03:00
monty@mysql.com	86508ad969	Fix test results	2004-12-06 01:34:19 +02:00
sergefp@mysql.com	838eaec709	Fix and testcase for BUG#4984 ... The crash is eliminated but still it is weird/inefficent that ROR-intersection is used when performing updates in empty table.	2004-08-11 16:40:46 +04:00
sergefp@mysql.com	dff98a8ef7	* New index_merge EXPLAIN output format ... * Fixed a problem with wrong query results for partially covering keys in ROR-index_merge * ROR-intersection retrieval plan choice algorithm now uses less disk IO - and properly processes clustered PK range scans * Fixed several minor range optimizer problems * Added more comments * Code cleanup	2004-05-29 02:04:01 +04:00
sergefp@mysql.com	a46d7542c9	This is first cset for WL#1394 "Optimize index merge when all involved index ranges include only values with equal keys" ... The main idea is to exploit the fact that key scans for "key=const" return ordered sequences of rowids.	2004-05-13 01:38:40 +04:00