-
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
Check for non-cacheable entities on metadata level, not at runtime #1433
Check for non-cacheable entities on metadata level, not at runtime #1433
Conversation
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-3783 We use Jira to track the state of pull requests and the versions they got |
Any news /feedback on this? |
* | ||
* @return array | ||
*/ | ||
public function getAssociationCacheDefaults ($fieldName, array $cache) |
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.
Extra space between the function name and open parenthesis
Besides minor CS fixes, looks good for me. Thanks @goetas |
done! thank you for reviewing my code |
This is gonna be in |
Check for non-cacheable entities on metadata level, not at runtime
This PR moves the check for non-cacheable entities from "runtime" to metadata definition.
If an entity has an association key as part of its PK, and this association key is not configured to be stored into SLC, an exception it thrown.
The previous approach was checking this constraint at "runtime" (right before saving the value), this PR moves this check at metadata level into (
_validateAndCompleteAssociationMapping
method).testQueryNotCacheableAssociationException
ther has been removed since this constraint is checked at metadata class loading time