Use subqueryload for all joins in get_screenshots #920
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.
What kind of change does this PR introduce?
This PR fixes a bug with loading strategies
Summary
FIxes a bug where different loading strategies are used to access the same relation, resulting in a mapping error. This is fixed by using the same
subqueryload
across all loads, as it is recommended for loading data when the related data is in large numbersChecklist
How can your code be run and tested?
Run the project, go to any recording detail page, and ensure that the page is rendered with the correct screenshots and action event data
Other information