michaellunsford Posted December 4, 2012 Share Posted December 4, 2012 So, I have SELECT * FROM `calendar` WHERE `DATE` >= '2012-12-04' ORDER BY `DATE` ASC LIMIT 0,30 The database hits some 10,000 records to find out which ones are today or future, which can really clock the database. Is there a way to manipulate the query or database so that it knows not to hit all 10,000 records in the search? I'd rather not separate the main table into two different ones, but that's about all I can come up with. Other ideas? Quote Link to comment Share on other sites More sharing options...
Barand Posted December 4, 2012 Share Posted December 4, 2012 Do you have an index on date column? Quote Link to comment Share on other sites More sharing options...
michaellunsford Posted December 4, 2012 Author Share Posted December 4, 2012 I'm not terribly good at indexes, but I just added one that includes the date field. Is it that easy, or do I need to write the query differently to take advantage? Quote Link to comment Share on other sites More sharing options...
Barand Posted December 4, 2012 Share Posted December 4, 2012 The question you should be asking is "Is it any faster with the index?" Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.