Skip to content

Update perform-two-phase-commits.txt #1592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update perform-two-phase-commits.txt #1592

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/tutorial/perform-two-phase-commits.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -456,17 +456,17 @@ Using Two-Phase Commits in Production Applications
The example transaction above is intentionally simple. For example, it
assumes that:

- it is always possible roll back operations an account.
- it is always possible roll back operations on an account.

- account balances can hold negative values.

Production implementations would likely be more complex. Typically
accounts need to information about current balance, pending credits,
accounts need information about current balance, pending credits,
pending debits. Then:

- when your application :ref:`switches the transaction state to
pending <2-phase-commits-step-2>` (i.e. step 2) it would also make
sure that the accounts has sufficient funds for the
sure that the account has sufficient funds for the
transaction. During this update operation, the application would
also modify the values of the credits and debits as well as adding
the transaction as pending.
Expand Down