From: Mike Bayer Date: Fri, 9 May 2008 17:28:43 +0000 (+0000) Subject: tweak X-Git-Tag: rel_0_5beta1~131 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=da44a7ac56207909f8dd61e70048f04175fe12a8;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git tweak --- diff --git a/doc/build/content/session.txt b/doc/build/content/session.txt index e8ec743c31..be028d769b 100644 --- a/doc/build/content/session.txt +++ b/doc/build/content/session.txt @@ -236,7 +236,7 @@ The solution is to use proper cascading: ### Flushing -When the `Session` is used with its default configuration, the flush step is nearly always done transparently. Specifically, the flush occurs before any individual `Query` is issued, as well as within the `commit()` call before the transaction is committed. This behavior can be disabled by constructing `sessionmaker()` with the flag `autoflush=False`. +When the `Session` is used with its default configuration, the flush step is nearly always done transparently. Specifically, the flush occurs before any individual `Query` is issued, as well as within the `commit()` call before the transaction is committed. It also occurs before a SAVEPOINT is issued when `begin_nested()` is used. The "flush-on-Query" aspect of the behavior can be disabled by constructing `sessionmaker()` with the flag `autoflush=False`. Regardless of the autoflush setting, a flush can always be forced by issing `flush()`: