-
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
11783 failure with indexed relation #11792
base: 2.20.x
Are you sure you want to change the base?
11783 failure with indexed relation #11792
Conversation
867f8c9
to
dae1522
Compare
Also, please squash the commits together (since you wouldn't revert one without the others, right?), and improve the remaining commit message according to the contributing guide. Specifically, explain both the bug and the fix. |
b0766d6
to
43d33aa
Compare
done |
@greg0ire The problem with phpstan checking still exists, it should be fixed in a separate commit |
See #11793 |
43d33aa
to
47a3015
Compare
Rebased PR |
if you are doing 2 things in one commit, that's bad. You should be doing 2 commits with clear messages, so that if one of them is wrong, it can be understood and reverted while the other stays. |
The bug related (doctrine#11694) and fixed mapping of sql column alias to field in entity (doctrine#11783) and invalidate cache [cache/persisted/entity|cache/persisted/collection] when sql filter changes
47a3015
to
2b62d35
Compare
these 2 things can't be separated |
@@ -611,12 +616,13 @@ public function refresh(array $id, $entity, $lockMode = null) | |||
* | |||
* @return CollectionCacheKey | |||
*/ | |||
protected function buildCollectionCacheKey(array $association, $ownerId) | |||
protected function buildCollectionCacheKey(array $association, $ownerId, string $filterHash) |
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.
@greg0ire Is introducing a new argument to a protected method okay in a version-branch that's already released? It may break projects that are implementing the Abstract class.
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.
I didn't spot that one. You're right, it's a breaking change for extending classes, that suddenly need to have that extra argument, and for callers, that need to provide it.
@dbannik please resort to func_get_args()
. The new argument should be added in the next major release.
Fix issue #11783