Repository navigation
test: verify JDBC rollback retry before safe close - #239
Draft
philipgreat wants to merge 1 commit into
Draft
philipgreat wants to merge 1 commit into
philipgreat wants to merge 1 commit into
Conversation
This branch has not been deployed
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
1 participant
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.
Adds one SQLite-backed fault-injection case to the review-only #238 stack.
The first rollback throws after the business INSERT. The retry performs a real rollback. A proxy simulates commit-on-close if close happens before rollback confirmation; the test verifies exactly two rollback attempts, safe close, no abort, and zero persisted rows after reopening.
Local source gate: focused JdbcRollbackCloseSqliteTest 4/4 twice; complete teaql-sqlite Maven reactor 295 tests, 0 failures, 0 errors, 1 existing skip; git diff --check clean.
This is a test-only draft. It does not change the pinned #238 head or reuse its internal-artifact/generated-consumer receipt. If incorporated into #238, requalify the changed exact head before formal-chain integration.