diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-02-03 00:42:22 +0000 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-02-03 00:42:22 +0000 |
| commit | faeeb99a2100465814f2b74c74cde275c52cd119 (patch) | |
| tree | 6f52c3ca3a7aa3eb72b24e63a2b0567d6624d3f8 /doc | |
| parent | 3227aefc7127902cc491a124a0a69c915d3d3af8 (diff) | |
| download | sqlalchemy-faeeb99a2100465814f2b74c74cde275c52cd119.tar.gz | |
switched objectstore begin/commit behavior to do "reentrant counter"
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/build/content/unitofwork.myt | 22 |
1 files changed, 1 insertions, 21 deletions
diff --git a/doc/build/content/unitofwork.myt b/doc/build/content/unitofwork.myt index d3ddb2b36..83f78e804 100644 --- a/doc/build/content/unitofwork.myt +++ b/doc/build/content/unitofwork.myt @@ -83,27 +83,7 @@ objectstore.commit() </&> <p>As always, the actual database transaction begin/commit occurs entirely within the objectstore.commit() operation.</p> - - <p>Since the begin/commit paradigm works in a stack-based manner, it follows that any level of nesting of begin/commit can be used:</p> - <&|formatting.myt:code&> - # start with UOW #1 as the thread-local UnitOfWork - a = Foo() - objectstore.begin() # push UOW #2 on the stack - b = Foo() - objectstore.begin() # push UOW #3 on the stack - c = Foo() - - # saves 'c' - objectstore.commit() # commit UOW #3 - - d = Foo() - - # saves 'b' and 'd' - objectstore.commit() # commit UOW #2 - - # saves 'a', everything else prior to it - objectstore.commit() # commit thread-local UOW #1 - </&> + <p>At the moment, begin/commit supports the same "nesting" behavior as the SQLEngine (note this behavior is not the original "nested" behavior), meaning that repeated calls to begin() will increment a counter, which is not released until that same number of commit() statements occur.</p> </&> <&|doclib.myt:item, name="transactionnesting", description="Nesting UnitOfWork in a Database Transaction" &> <p>The UOW commit operation places its INSERT/UPDATE/DELETE operations within the scope of a database transaction controlled by a SQLEngine: |