-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkp/pkp-lib#3304 Replace homebrew caching with Stash #5743
base: main
Are you sure you want to change the base?
Conversation
c0516c2
to
bc2555d
Compare
$result->Close(); | ||
$pool->save($item->set($returner)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asmecher I'm wondering if this will cause a problem in cases where _fromRow()
fetches dependent entities. So let's say I've got a Submission
and it's in cache. Then I edit one of it's Publication
objects. I've cleared the cache on the Publication
object but not the Submission
. When I go to get the Submission
again it's going to return an object with nested Publication
s, one of which will be out of date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I'm still working out details here... Off the top of my head, I'd like to exclude dependent entities from the serialized object and have them fetched separately (from the cache if possible) if we're going to use "deep caching" throughout the system. Another option (which is what we used to do) is to enable persistent caching only for high-volume scenarios like the reader front-end where mid-request updates don't happen.
7fa2289
to
583dec4
Compare
No description provided.