Re: Optimizer Decisions change with Storage Engine [MyISAM, InnoDB]

[Drei Bit]

Will do the same.

But what I found out by further playing around was, that this behavior is also dependent on the like statement, even though it is always possible to do the range query, he will do some strange stuff like:

id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
1	PRIMARY	<derived2>	ALL	<null>	<null>	<null>	<null>	452459	
1	PRIMARY	a	eq_ref	PRIMARY	PRIMARY	4	x.id	1	
2	DERIVED	B	index	<null>	b_ix_dummy_id	772	<null>	452459	Using where; Using index

The strange point here is: why does he tell me there are no possible_keys (for me that should be named index ;).