Skip to content
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

When updating L2 cached object, make sure that any versioned field is also updated #304

Closed
andyjefferson opened this issue Aug 3, 2018 · 0 comments
Labels
Milestone

Comments

@andyjefferson
Copy link
Member

In an L2 cached object we store the "version" separately. In the case of a versioned field (as opposed to surrogate version) we don't currently enforce that this field is also updated in the L2 cache. There many be situations where the version is updated for optimistic check purposes, but the field is not marked as dirty. Consequently the L2 cached object doesnt get the field updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant