fix: Improve performance on asset screenshot retrieval #2248
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
When retrieving the related screenshot for a
Save
orState
, we were retrieving a very heavy representation of the associatedRom
object, only to iterate through its screenshots to find the one we needed.This change modifies the
Save
andState
models to directly query theScreenshot
model, which is much faster and more efficient. TheDBScreenshotsHandler
has been updated to include a newfilter
method that will simplify building queries using SQLAlchemy, something we can extend to other handlers in the future.Fixes #1925.
Checklist