Davi Arnaut 918a038165 Bug#36326: nested transaction and select ...

The problem is that the query cache stores packets containing
the server status of the time when the cached statement was run.
This might lead to a wrong transaction status in the client side
if a statement is cached during a transaction and is later served
outside a transaction context (and vice-versa).

The solution is to take into account the transaction status when
storing in and serving from the query cache.

2009-01-13 20:07:06 -02:00

69 KiB

Raw Blame History

View Raw