multi-instance relation fields; empty/notempty querying - part2 #18095
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Follow-up to #18092. It requires a signature change in the
BaseRelationField::existsQueryCondition()method, hence targeting 5.9.PR #18092 resolves an issue with querying an instance of the same field in a single field layout.
This PR takes that further and improves querying an instance of the same field (with the same handle) across multiple field layouts.
Steps to reproduce:
assetsfield (don’t override the handle)assetsfield for:empty:5.xbranch, only entry 5 is returnedbugfix/multi-instance-relation-field-empty-notempty-queryingbranch, entries 3, 5, 6 are returned:notempty:5.xbranch, entries 1, 2, 3, 4, 6 are returnedbugfix/multi-instance-relation-field-empty-notempty-queryingbranch, entries 1, 2, 4 are returnedRelated issues
n/a