if (is_disabled() || thd->locked_tables_mode || thd->variables.query_cache_type == 0)
DBUG_ASSERT(query_cache_size != 0); // otherwise cache would be disabled
DBUG_PRINT("qcache", ("\
long %d, 4.1: %d, bin_proto: %d, more results %d, pkt_nr: %d, \
CS client: %u, CS result: %u, CS conn: %u, limit: %lu, TZ: 0x%lx, \
sql mode: 0x%llx, sort len: %lu, conncat len: %lu, div_precision: %lu, \
def_week_frmt: %lu, in_trans: %d, autocommit: %d",
is this the "primary key" of the query cache!?!?!?!?!?!?!
could we use a sha1 or another "primary key" method (index [] of the query in cache + '';'+ 5 bytes of a hash key to compare if the index still with the same query)
to easly show query entry "number", and allow a "delete from query_cache_information where key=xxx" function?
at line 1938 we have this maybe the query position on cache ("primary key of query cache")?:
DBUG_PRINT("qcache", ("Query have result 0x%lx", (ulong) query));
there's some more ideas about query cache information plugin at MDEV-4571, if anyone could read it =)