Sorry for wrong answer, actually, that's the behavior of oracle query cache, so I guessed it would be same for MySQL too. I sincerely apologize for any inconvenience caused.
Nitin ----- Original Message ----- From: "Dan Nelson" <[EMAIL PROTECTED]> To: "Nitin" <[EMAIL PROTECTED]> Cc: "Reto Baumann" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, October 13, 2003 12:03 AM Subject: Re: How does LIMIT affect Query Caching > In the last episode (Oct 12), Nitin said: > > query cache doesn't cache the data, but the execution plan of the > > query. so, in your example it'll treat both query as same, as both > > are fetching data from same result set. query cache just increases > > the speed of query "execution", that means minimizes the time taken > > to actually execute the query, not the time taken to fetch the data > > from the database. > > Actually, the query cache doesn't cache the execution plan; it caches > the query string, so any difference from query to query, including > spaces and capitalization, is important. > > http://www.mysql.com/doc/en/Query_Cache_How.html > > -- > Dan Nelson > [EMAIL PROTECTED] > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
