feat: implement database transaction management for critical operations#525
Merged
Qoder-Undefined merged 1 commit intoJun 29, 2026
Conversation
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.
Summary
Implements explicit database transaction management for critical multi-write operations in the
meridian-api, addressing the risk of partially persisted data when one write succeeds and a subsequent one fails.Changes
src/common/providers/database-transaction.provider.ts— New reusableDatabaseTransactionProviderservice wrapping any callback in aQueryRunnertransaction: connects, begins, commits on success, rolls back + logs on failure, and always releases the runner.src/post/provider/post.service.ts—createPostandUpdatePostnow execute inside explicitQueryRunnertransactions. The post row, cascadedMetaOptionsave, and tag join-table writes are applied atomically; any failure triggers a full rollback.src/common/providers/database-transaction.provider.spec.ts— Unit tests covering commit on success and rollback-on-error for the new provider.src/post/provider/post.service.spec.ts— Updated tests covering both happy-path transaction commits and rollback scenarios forcreatePostandUpdatePost.closes #524