[DDC-1563] Result cache for repository queries Created: 25/Dec/11 Updated: 26/Aug/12
|Project:||Doctrine 2 - ORM|
|Reporter:||Benjamin Eberlei||Assignee:||Fabio B. Silva|
Many related "standing data" tables are very static and seldom change. There should be a metadata config to enable result cache for ALL repository operations.
|Comment by Benjamin Eberlei [ 25/Dec/11 ]|
This should directly support cache invalidation through a tag. Each repository gets a key with the current version. The version is one part ofthe actual cache datas key.
A new cache key version is generated:
1. When none is found during find operation
For transaction consisteny the rollback operation in UoW needs to reset cache keys and only after a succesful commit operation the new cache key version should be set.
We may need begin, commit, rollback events in UoW for this.