I have a table in a MySQL database that I need to optimise the speed of searching on. It looks like this:
CREATE TABLE some_table ( key CHAR(50), val1 CHAR(10), val2 INT, PRIMARY KEY (key) )
The select that has to run against it is very simple and looks like
SELECT * FROM some_table WHERE key = ? OR key = ? OR key = ?
There are no like operators and the statement handles are all prepare cached and cached themselves with the bind values passed to the execute as needed. Implicit in the MySQL docs is the notion that a B-tree index is automatically created for the primary key. It is not however explicit. So the question is does a primary key need an index to optimise search speed?
Having just written this the obvious answer is just to test it I guess. Still I am lazy enough to seek the wisdom of the monks as a shortcut...
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
In reply to MySQL Select Speed Optimisation by tachyon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |