yay!

I have bugged MySQL for a couple of years to document that. I believe there used to be a comment from me in the manual about it.

The bitch of the thing is that it doesn't always work. Even if you tell MySQL to use an index sometimes it won't. I have a couple of queries that every so often will just skip around to different indexes (which cause the frontpage to Slashdot to load slowly). I've shown the problem to Monty before but I don't think I ever got an answer from him about a solution.

http://www.mysql.com/doc/en/SELECT.html

In MySQL 4.0.9 you can also use FORCE INDEX. This acts likes USE INDEX (key_list) but with the addition that a table scan is assumed to be VERY expensive. In other words a table scan will only be used if there is no way to use one of the given index to find rows in the table.

Eh. Sometimes it takes being stupid to learn, and be happy. Wait, duh. That whole sentence was stupid. But now I'm happy? ::shrug:: Seems I've taken on the role of Captain Obvious today. Oh well. There I go again. And again. I need to shut up. And there I am stating the obvious again!

Well, good for you! I'll shut up for everyone's sake now. :-D

hmmm? noticeable huh? cool!!

Won't you be, my neighbor ???

HELLO NEIGHBOR!

I'm really glad I read this. Hard ass.

After having people tell me for about four years that “MySQL's query optimiser will sort it out”, this is quite a surprise.

Oh well.

It works well for constants, but not for ranges, from what I can tell.