Improve data consistency and prevent orphaned records in user/tenant management #732
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.
CHANGELOG.md
Pull Request type
Makes the transactions atomic when it's relevant to maintain data consistency and integrity. The decorated methods perform multiple database operations. If an error occurs at any step (e.g., a database integrity error, a connection issue, or an unexpected exception), we could end up with a partially updated state where some changes are applied but not all. Wrapping these operations in
transaction.atomic
ensures that either all changes are applied or none at all. If anything goes wrong, all changes are rolled back, ensuring the database remains in a valid state.Also, if multiple processes or threads are executing these methods simultaneously, there is a risk of race conditions. Django’s
transaction.atomic
helps mitigate issues by ensuring that all modifications within the block are treated as a single unit.Related issue(s)