From: Jason Kirtland <jek@discorporate.us>
Date: Wed, 21 May 2008 18:25:44 +0000 (+0000)
Subject: - Docstring fix.
X-Git-Tag: rel_0_5beta1~36
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d1c80500c5f125f250441ec9299f63d73b1c3d58;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

- Docstring fix.
---

diff --git a/lib/sqlalchemy/orm/session.py b/lib/sqlalchemy/orm/session.py
index ab62292634..a651d4a0a1 100644
--- a/lib/sqlalchemy/orm/session.py
+++ b/lib/sqlalchemy/orm/session.py
@@ -89,12 +89,12 @@ def sessionmaker(bind=None, class_=None, autoflush=True, autocommit=False,
 
     autoflush
       When ``True``, all query operations will issue a ``flush()`` call to
-     this ``Session`` before proceeding. This is a convenience feature so that
-     ``flush()`` need not be called repeatedly in order for database queries
-     to retrieve results. It's typical that ``autoflush`` is used in
-     conjunction with ``autocommit=False``.  In this scenario, explicit calls
-     to ``flush()`` are rarely needed; you usually only need to call
-     ``commit()`` (which flushes) to finalize changes.
+      this ``Session`` before proceeding. This is a convenience feature so
+      that ``flush()`` need not be called repeatedly in order for database
+      queries to retrieve results. It's typical that ``autoflush`` is used in
+      conjunction with ``autocommit=False``.  In this scenario, explicit calls
+      to ``flush()`` are rarely needed; you usually only need to call
+      ``commit()`` (which flushes) to finalize changes.
 
     bind
       An optional ``Engine`` or ``Connection`` to which this ``Session``