Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2.2.1
-
Component/s: cache
-
Labels:None
-
Sprint:2017-44
Description
Hi,
From our lunch talk I got the impression that the cache module is not ACID compliant:
SELECT statements inside a read/write transactions return cached results. This means the statement is not sent to the server which means the read locks are not set. With REPEATABLE-READ (or SERIALIZABLE) isolation level this makes it not ACID compliant.
Please change this so read/write transactional reads do not return cached results.
Thanks,
Michaël