You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In grails 2, applying cache true in a parent domain class's mapping block would propagate 2nd level caching through to the child domains, this is not the case with grails 4.
This results in attempted retrievals and misses from the cache for the child domain.
The linked sample project displays this behaviour by setting up a Parent and Child domain & calls to both dynamic finder and criteria queries through loading of the index page.
The logged session statistics show that the domain details never seem to be put into the cache.
A non-abstract domain (StandardThing) is also configured to ensure the correct behaviour which can be accessed through the relevant URI.
I updated my build.gradle dependencies to include this fix #483 . I would suggest you try to update your sample app dependencies as well to see if it has any effect.
I think we are reporting the same issue although my example does not use an abstract parent class. #692
In grails 2, applying cache true in a parent domain class's mapping block would propagate 2nd level caching through to the child domains, this is not the case with grails 4.
This results in attempted retrievals and misses from the cache for the child domain.
The linked sample project displays this behaviour by setting up a Parent and Child domain & calls to both dynamic finder and criteria queries through loading of the index page.
The logged session statistics show that the domain details never seem to be put into the cache.
A non-abstract domain (StandardThing) is also configured to ensure the correct behaviour which can be accessed through the relevant URI.
Sample app
https://github.com/leadtrip/grail4AbstractCache
The text was updated successfully, but these errors were encountered: