database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-30 16:24:05 +03:00
Code Activity

Merge

Browse Source
This commit is contained in:
Igor Babaev
2010-12-28 12:25:33 -08:00
parent 0dc5ef87d4 dccc01a82a
commit ea7082aee2
2 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
sql/opt_range.cc
View File

@ -5711,8 +5711,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);
} }

3
sql/opt_range.h
View File

@ -515,8 +515,7 @@ public:
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