execute update query in batch to avoid slow bulk action query #3280
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
0_0 Was going to ask about this as some of the clean up features will rely heavily on bulk. |
|
@jacksonh i think this still might not be the best way to achieve incremental update but that's so far the best way i can do: in the db transaction:
let me know if you got some better idea or alternatives 👍 |
|
similar idea could be applied to prune user accounts -- incremental delete of library items and then delete user account |
… result set could change during update
sywhb
force-pushed
the
fix/slow-db-query
branch
from
1e1bcc3 to
b5d8409
Compare
jacksonh
approved these changes
Dec 29, 2023
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.
No description provided.