From: Lele Gaifax Date: Mon, 4 Aug 2008 13:17:40 +0000 (+0000) Subject: Typo X-Git-Tag: rel_0_5beta3~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=28ff190475b1717a7cb8616a7ad8590c00a9a6c8;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Typo --- diff --git a/doc/build/content/session.txt b/doc/build/content/session.txt index 6f7016deeb..7f8d06f906 100644 --- a/doc/build/content/session.txt +++ b/doc/build/content/session.txt @@ -238,7 +238,7 @@ The solution is to use proper cascading: 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()`: +Regardless of the autoflush setting, a flush can always be forced by issuing `flush()`: {python} session.flush()