CODEBLIX / TX58

Batch transaction workspace

Define the failure boundary. Inspect the candidate. Decide the commit.

Oracle development consultation →
Source TX58-S1 · candidate r1
Candidate stateNot runAll or nothing
Staged changes0 / 3Committed separately
Rejected inputs—Whole numbers 0–999
Committed control sum · units2412 + 7 + 5

Incoming reorder-point changes

Each target key appears once. Rows run in source order.

RowTargetCommittedIncomingValidation

Rule: a reorder point is an integer from zero to 999 units.

Transaction decision contract

  1. All or nothing: stop at the first invalid row and discard every staged change.
  2. Row savepoint: reject that row, retain its prior value and continue with eligible rows.
  3. Commit decision: Release owner publishes a current candidate containing changes.

The committed control is separate from the candidate until that decision.

Run the original source to inspect how row 2 affects the batch.