Hi! > In MySQL 4.0, query cache hits are counted in Qcache_hits, but not in > Com_select. The documentation for Com_select implies that they should be > there. Is this the intended behavior, or is it a bug? > > - JD
It is intended behaviour. Com_select is incremented each time SELECT query is executed. But if a query is found in a query cache it's not executed, it's not even parsed - cached result is immediately sent back. Following this logic, Com_select is not incremented for a query cache hits.. Regards, Sergei -- MySQL Development Team __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany <___/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
