feat: use database transactions for the bulk generation #157
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 does it do?
Handle bulk generation using database transactions.
Why is it needed?
Because bulk generating the URL aliases could potentially be a very large task. Using database transactions we can assure the database is not in a "half" broken state mid bulk generation.
How to test it?
Test the different features of the bulk generation feature.
Related issue(s)/PR(s)
#13
Todo