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
I'm experiencing an issue while configuring the SecondLevelCache. I still have to figure out correctly how it works (the docs are not very verbose on the topic), so actually I have messed up with many parameters.
I found a bug while caching entities which have non-owning OneToOne relationship: in these case, if the relation is not marked as @Cacheable, i got the message Undefined index: targetToSourceKeyColumns. This issue never happens on the owning side.
I was able to track down the issue, and the commit here just expose the issue in some existing tests.
I'm sorry I cannot give you a proper patch, but I don't know if the problem reside in the Hydrator logic, in the association class (since targetToSourceKeyColumns and sourceToTargetKeyColumns are unset) or in the configuration validation.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of giosh94mhz:
Url: #1544
Message:
I'm experiencing an issue while configuring the SecondLevelCache. I still have to figure out correctly how it works (the docs are not very verbose on the topic), so actually I have messed up with many parameters.
I found a bug while caching entities which have non-owning OneToOne relationship: in these case, if the relation is not marked as
@Cache
able, i got the messageUndefined index: targetToSourceKeyColumns
. This issue never happens on the owning side.I was able to track down the issue, and the commit here just expose the issue in some existing tests.
I'm sorry I cannot give you a proper patch, but I don't know if the problem reside in the Hydrator logic, in the association class (since targetToSourceKeyColumns and sourceToTargetKeyColumns are unset) or in the configuration validation.
The text was updated successfully, but these errors were encountered: