Oracle 5.0 Reference Manual page 2713

Mysqlnd query result cache plugin (mysqlnd_qc)
Statistic
query_found_in_cache
query_uncached_other
query_uncached_no_table
query_uncached_use_result
query_aggr_run_time_cache_hit
query_aggr_run_time_cache_put
query_aggr_run_time_total
query_aggr_store_time_cache_hit
Description
may not be added to the cache
later on.
Statement is considered
cacheable and we have found
it in the cache but we have not
replayed the cached data yet
and we have not send the result
set to the client yet. This is not
considered a cache hit because
the client might not fetch the
result or the cached data may be
faulty.
Statement is considered
cacheable and it may or may not
be in the cache already but either
replaying cached data has failed,
no result set is available or some
other error has happened.
Statement has not been cached
because the result set has at
least one column which has no
table name in its meta data.
An example of such a query is
SLEEP(1). To cache
SELECT
those statements you have to
change default value of the
PHP configuration directive
mysqlnd_qc.cache_no_table
and set
mysqlnd_qc.cache_no_table
1. Often, it is not desired to
=
cache such statements.
Statement would have been
cached if a buffered result set
had been used. The situation
is also considered as a cache
miss and
cache_miss
incremented as well.
Aggregated run time (ms) of
all cached queries. Cached
queries are those which have
incremented cache_hit.
Aggregated run time (ms) of all
uncached queries that have been
put into the cache. See also
cache_put.
Aggregated run time (ms) of all
uncached and cached queries
that have been inspected and
executed by the query cache.
Aggregated store time (ms)
of all cached queries. Cached
2693
Version
Since 1.0.0.
Since 1.0.0.
Since 1.0.0.
will be
Since 1.0.0.
Since 1.0.0.
Since 1.0.0.
Since 1.0.0.