[DDC-2248] Expire result cache functionality not implemented Created: 19/Jan/13 Updated: 01/Oct/15
|Project:||Doctrine 2 - ORM|
|Affects Version/s:||2.3, 2.3.1, 2.3.2|
|Reporter:||Piotr Niziniecki||Assignee:||Benjamin Eberlei|
According to documentation expireResultCache, should force cache to update but it's not working... Why? Because functionality is not implemented. You can set _expireResultCache variable, but there is no place where this variable is being checked.
|Comment by Marco Pivetta [ 19/Jan/13 ]|
A cache profile can be set and cleaned. I suppose that `expireResultCache` is an old piece of code that survived the refactoring. Should just be removed and documented accordingly
|Comment by Michael Dwyer [ 01/Oct/15 ]|
My understanding was that expireResultCache would ignore the cache, execute the query, and then save the result to cache. I'm not sure how accomplish that same thing by manipulating the cache profile, unless I created a result cache driver that always returned false on fetch, and used it for these occasions.
Am I missing something or is that a use case that shouldn't happen?