diff options
| author | Corey Farwell <coreyf@rwell.org> | 2014-09-02 23:27:36 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-09-03 11:49:00 -0400 |
| commit | 4db75925be90affaf49ffe5361b47a56762f93d0 (patch) | |
| tree | 20259e791bb990e7f2ec80b04c522f74a0632148 | |
| parent | 09c1f18f223cd60c948f7dae6aedccea70a92274 (diff) | |
Fixed typo in docs/topics/db/transactions.txt.
| -rw-r--r-- | docs/topics/db/transactions.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 06b8285652..fb19666c43 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -575,7 +575,7 @@ the block of code it controls; when exiting the block, it commits or rollbacks, and switches back to auto mode. So :func:`commit_on_success` really has two effects: it changes the -transaction state and it defines an transaction block. Nesting will give the +transaction state and it defines a transaction block. Nesting will give the expected results in terms of transaction state, but not in terms of transaction semantics. Most often, the inner block will commit, breaking the atomicity of the outer block. |