fix: Filter returned entity result by view columns #881
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.
When updating rows in a view I noticed a but where the second update operation of the same row wold fail in the frontend.
It turned out that the first update would actually return a column that was not in the view itself which it tried to update then on the next attempt.
This PR introduces filtering for the actual columns of a view in places where we return its data (update/delete).
Steps to reproduce: