Hvis jeg udfører det, du gjorde ovenfor, får jeg
EXPLAIN select * from stats_clicked s
join visitor v on s.visitor_id=v.id
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+
| 1 | SIMPLE | v | ALL | PRIMARY | NULL | NULL | NULL | 15 | NULL |
| 1 | SIMPLE | s | ref | index3,index1 | index3 | 4 | so_gibberish2.v.id | 1 | Using index |
+----+-------------+-------+------+---------------+--------+---------+--------------------+------+-------------+
Men hvis jeg afkorter, skal du udføre følgende belastning af en masse data (ender med over 100.000 rækker):
truncate table visitor;
insert into visitor (`visited_time`) values
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944),
(1467122944),(1467122944),(1467122944);
insert into visitor (`visited_time`) values
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
(1467122945),(1467122945),(1467122945),
insert into visitor (`visited_time`) values
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946),
(1467122946),(1467122946),(1467122946);
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
insert visitor(`visited_time`) select `visited_time` from visitor;
select count(*) from visitor;
-- 104448 rows
Dette resulterer i IKKE en tabelscanning:
EXPLAIN select * from stats_clicked s
join visitor v on s.visitor_id=v.id;
+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+
| 1 | SIMPLE | s | index | index3,index1 | index3 | 9 | NULL | 22 | Using index |
| 1 | SIMPLE | v | eq_ref | PRIMARY | PRIMARY | 4 | so_gibberish2.s.visitor_id | 1 | NULL |
+----+-------------+-------+--------+---------------+---------+---------+----------------------------+------+-------------+
Årsagen er angivet på manualsiden Hvordan MySQL bruger indekser :
Årsagen er nævnt ovenfor. I dit spørgsmåls eksempel havde du for få rækker til at gøre brugen af indekset det værd. Så db-motoren valgte sin angiveligt (og sandsynligvis) hurtigere måde at ikke bruge indekset på dit lille bord på.