Allow map calculated DB field to entity property #6263
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.
Imagine that you want to restrict delete action on entities with relation by other entities.
And you don't want/can't use cascade behavior.
In such case you need to do additional query (or maybe much more if relation has fetch eager fields) for every entity in index page.
With proposed fix you can
addSelect
increateIndexQueryBuilder
and it will be mapped correctly.For example you have Category and Product and want to restrict delete category if it has products.
As bonus you can get product count in category within one query.
Like