We're tracking an issue with a race condition in cache-money. It should only affect people who use a combination of cached and uncached models.
The issue occurs because transactional updates are written to cache before the database transaction commits. In our case, we have a cached parent model with an uncached collection. The parent and collection are updated in a transaction but due to the parent being cached, the update to that record is visible to other requests before the dependent collection updates.
Two solutions appear to be
make sure all involved records are cached
wrap the database transaction in another cache transaction so that the cache buffer is only flushed after the database commits
We're tracking an issue with a race condition in cache-money. It should only affect people who use a combination of cached and uncached models.
The issue occurs because transactional updates are written to cache before the database transaction commits. In our case, we have a cached parent model with an uncached collection. The parent and collection are updated in a transaction but due to the parent being cached, the update to that record is visible to other requests before the dependent collection updates.
Two solutions appear to be