-
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
DDC-3259: Second level & UnitOfWork inconsistencies #4048
Comments
Comment created by @Ocramius: [~goetas] do you have any example of where this may be happening? |
Comment created by goetas: This is the same branch of #1113, plus this commit (goetas@bfbbb91) that simply involves the second level cache too. |
Comment created by @doctrinebot: |
Comment created by goetas: Here the failure https://travis-ci.org/doctrine/doctrine2/jobs/32972996#L402 |
Comment created by @doctrinebot: |
Comment created by @doctrinebot: |
Comment created by @doctrinebot: |
1 similar comment
Comment created by @doctrinebot: |
Comment created by @doctrinebot: |
Looks like it was fixed on #1113 (which was merged manually). |
Jira issue originally created by user goetas:
Hi!
I have a lot of entities with entity associations as keys and I'm trying to use second level cache.
Looking at the method:
UnitOfWork::createEntity($className, array $data, &$hints = array())
$className
: contains the class name$data
: contains the raw data (the row coming from the database)Enabling the second level cache,
DefaultQueryCache::get
calls thecreateEntity
method passing a$data
that contains object entities and some raw data (https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Cache/DefaultQueryCache.php#L155).I think that
DefaultQueryCache
should not introduce a variant of$data
and should create a compatible version of$data
.The text was updated successfully, but these errors were encountered: