summaryrefslogtreecommitdiff
path: root/sql/key.cc
diff options
context:
space:
mode:
authorSergei Golubchik <serg@mariadb.org>2017-02-02 00:47:07 +0100
committerSergei Golubchik <serg@mariadb.org>2017-02-13 18:12:05 +0100
commite46c42217f4fc7ba43992ca54c039f2556d1859f (patch)
treececd39b5d2528eb4ff102e1a86f2a17aec6cc0dc /sql/key.cc
parent460ff39871d6554ec17714a79a174cf8f80f7817 (diff)
downloadmariadb-git-e46c42217f4fc7ba43992ca54c039f2556d1859f.tar.gz
cleanup: TABLE::mark_columns_used_by_index()
mark_columns_used_by_index used to do reset + mark_columns_used_by_index_no_reset + start keyread + set bitmaps Now prepare_for_keyread does that, while mark_columns_used_by_index does only reset + mark_columns_used_by_index_no_reset, just as its name suggests.
Diffstat (limited to 'sql/key.cc')
-rw-r--r--sql/key.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/sql/key.cc b/sql/key.cc
index 3bb009fcac9..bb10e902b8b 100644
--- a/sql/key.cc
+++ b/sql/key.cc
@@ -465,8 +465,7 @@ void key_unpack(String *to, TABLE *table, KEY *key)
bool is_key_used(TABLE *table, uint idx, const MY_BITMAP *fields)
{
- bitmap_clear_all(&table->tmp_set);
- table->mark_columns_used_by_index_no_reset(idx, &table->tmp_set);
+ table->mark_columns_used_by_index(idx, &table->tmp_set);
return bitmap_is_overlapping(&table->tmp_set, fields);
}