Commit e8adeac3 authored by Igor Babaev's avatar Igor Babaev

Merge

parents e99e7fb1 142b9bac
...@@ -5623,8 +5623,7 @@ ROR_SCAN_INFO *make_ror_scan(const PARAM *param, int idx, SEL_ARG *sel_arg) ...@@ -5623,8 +5623,7 @@ ROR_SCAN_INFO *make_ror_scan(const PARAM *param, int idx, SEL_ARG *sel_arg)
bitmap_set_bit(&ror_scan->covered_fields, key_part->fieldnr-1); bitmap_set_bit(&ror_scan->covered_fields, key_part->fieldnr-1);
} }
ror_scan->index_read_cost= ror_scan->index_read_cost=
param->table->file->keyread_time(ror_scan->keynr, 1, param->table->file->keyread_time(ror_scan->keynr, 1, ror_scan->records);
param->table->quick_rows[ror_scan->keynr]);
DBUG_RETURN(ror_scan); DBUG_RETURN(ror_scan);
} }
......
...@@ -482,8 +482,7 @@ class QUICK_RANGE_SELECT_GEOM: public QUICK_RANGE_SELECT ...@@ -482,8 +482,7 @@ class QUICK_RANGE_SELECT_GEOM: public QUICK_RANGE_SELECT
Current implementation doesn't detect all cases where index merge could Current implementation doesn't detect all cases where index merge could
be used, in particular: be used, in particular:
* index merge+'using index' is not supported (this the consequence of * index_merge+'using index' is not supported
the above restriction)
* If WHERE part contains complex nested AND and OR conditions, some ways * If WHERE part contains complex nested AND and OR conditions, some ways
to retrieve rows using index merge will not be considered. The choice to retrieve rows using index merge will not be considered. The choice
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment