-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
ORM second level cache and version (locking) #7067
Comments
This is way too little information to work on anything. Please try re-creating a failure with an isolated test. See examples at https://github.com/doctrine/doctrine2/tree/master/tests/Doctrine/Tests/ORM/Functional/Ticket |
I have never done it before. Here is the fast fix:
This can fix the problem. |
@Ocramius hi again, I need some help. |
@wtorsi you first need to fork this repository (top right on this page), then follow https://yangsu.github.io/pull-request-tutorial/ 👍 |
Thank's |
for doctrine version 3
Got it, here is the test. |
As explained in doctrine#7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
As explained in doctrine#7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
As explained in doctrine#7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
Test for Second level cache with Version, DDC #7067
As explained in #7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
Fixed by #7069 |
As explained in doctrine#7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
As explained in #7067, fields with `@ORM\Version` annotation were not being added to L2C cached data.
Hi,
I have found strange behaviour when using Second Level Cache and Version.
When new version is set second level cache does not include it into update.
After some investigation:
The problem occurs here
DefaultEntityHydrator::buildCacheEntry
, UnitOfWork does not include version field in actualData.Any ideas how to fix it?
The text was updated successfully, but these errors were encountered: