Re: Composite index

[Julian Assange]

Hi!

Sorry, I missed to paste the PK on the create statement...

....
PRIMARY KEY (`id`),
....

Not sure why the optimizer would think it is dealing with innodb when the table is a Myisam. It does not say much for how smart the optimizer is if its unable to work out the nature of the table.

Changing the query to SELECT 1... makes no difference, primary is still in use.

mysql> explain select 1 from users where id = 828191 and cookie = 1656382;
+----+-------------+------------+-------+---------------------------+---------+---------+-------+------+-------+
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
+----+-------------+------------+-------+---------------------------+---------+---------+-------+------+-------+
| 1 | SIMPLE | users | const | PRIMARY,idcookie | PRIMARY | 4 | const | 1 | |
+----+-------------+------------+-------+---------------------------+---------+---------+-------+------+-------+



Yeah, almost at all times the query should return true as users browse through with their cookie authenticating them.

The subsequent queries are mostly unrelated to the content of that table.

I dont use innodb because 1. it appears myisam is best for mostly selects and not so much update 2. I understand better how it works 3. I have used innodb in a smaller project and the size of a file ibdata1 has grown huge for a small database.