Use a simpler database fetch in fullUpdateFromOld #3615
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
advplyr
reviewed
Nov 21, 2024
| { | ||
| model: this.sequelize.models.series, | ||
| through: { | ||
| attributes: ['id', 'sequence'] |
There was a problem hiding this comment.
Turns out we were using the bookSeries.id to handle updating series sequence. #3636
I looked for this specifically and didn't see it. Just an fyi
There was a problem hiding this comment.
Good catch. I didn't notice the difference.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is followup to #3604.
As discussed privately, the database fetch in
LibraryItem.fullUpdateFromOldcauses a memory spike because of the query complexity. This uses a simpler query to achieve the same result.