Fix/589 db transactions - #619
Merged
Abdulazeem-code merged 7 commits intoSep 3, 2026
Merged
Conversation
|
@Peolite1 is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@Peolite1 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Owner
|
FIX FAILED CHECKS AND RESOLVE CONFLICTS |
Contributor
Author
done |
Owner
|
FIX FAILED CHECKS |
Owner
|
FIX FAILED CHECKS |
Contributor
Author
done |
This file contains hidden or 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
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.
Implement database transaction wrapping for multi-step mutations
Closes #589
Description
This PR implements database transaction wrapping for endpoints that perform multi-step database mutations to ensure atomic operations and prevent partial state corruption on failure.
Previously, several endpoints (such as those handling user creation and cache invalidation, or webhook creation) ran operations in sequence without transaction wrapping. If an exception occurred midway, it left the system with partial or inconsistent data.
Changes Made
prismaClient.js: Added a newwithTransactionutility wrapper to provide a consistent abstraction overprisma.$transaction. Also updated the mock database$transactionto support Prisma's interactive transaction format.src/routes/v1/userRoutes.js): Wrapped user creation and cache invalidation inside the transaction utility.src/routes/v1/adminRoutes.js): Wrappedprisma.user.updateand the subsequent stats/federation cache invalidation inside the transaction utility.src/routes/v1/webhookRoutes.js): Wrapped webhook creation inside the transaction utility.Acceptance Criteria Met
Impact
Prevents data corruption from partial writes during database, logic, or network failures.