You execute this EXPLAIN statement for a SELECT statement on the table named comics.which contains 1183 rows:

Mysql> explain select comic_ title, publisher from comics where comic_title like `& Action&'; row in set (0.00 sec) You create the following index:

CREATE INDEX cimic_title_idx ON comics (comic_title, publisher); You run the same EXPLAIN statement again; Mysql > explain select comic_title ,publisher from comics where comic_title like `& Action&'; 1 row inset (0.00 sec) Why didthe second SELECT statement need to read all 1183 rows in the index comic_title_idx?

Question

You execute this EXPLAIN statement for a SELECT statement on the table named comics.which contains 1183 rows:

Mysql> explain select comic_ title, publisher from comics where comic_title like `& Action&'; row in set (0.00 sec) You create the following index:

CREATE INDEX cimic_title_idx ON comics (comic_title, publisher); You run the same EXPLAIN statement again; Mysql > explain select comic_title ,publisher from comics where comic_title like `& Action&'; 1 row inset (0.00 sec) Why didthe second SELECT statement need to read all 1183 rows in the index comic_title_idx?

Accepted Answer

D. Because a wildcard character is at the beginning of the search word

Answer

A. Because comic_title is not the primary key

Answer

B. Because a LIKE statement always requires a full tables scan

Answer

C. Because comic _title is part of acovering index

You execute this EXPLAIN statement for a SELECT statement on the table named comics.which contains 1183 rows: Mysql> explain select comic_ title, publisher from comics where comic_title like &…

Question

Exhibits

Options

How the community answered

Community Discussion