diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-11-17 11:30:56 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-11-17 11:30:56 -0500 |
| commit | 7c3de81ee06b3cda03839bbbf85f89fd572551bf (patch) | |
| tree | 45b9013d3520bce0df6935e834932c5abddd3053 | |
| parent | e469529a1dd01f58eca2291eff3f38fe61c1175e (diff) | |
| parent | 65e66cdf3714c10824c789e2931cd1311ea3eeef (diff) | |
| download | sqlalchemy-7c3de81ee06b3cda03839bbbf85f89fd572551bf.tar.gz | |
Merged in idank/sqlalchemy (pull request #27)
| -rw-r--r-- | doc/build/orm/session.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/orm/session.rst b/doc/build/orm/session.rst index 7b00f4eb5..d5cc21e82 100644 --- a/doc/build/orm/session.rst +++ b/doc/build/orm/session.rst @@ -42,7 +42,7 @@ held by the :class:`.Session` - there are a variety of events that will cause objects to re-access the database in order to keep synchronized. It is possible to "detach" objects from a :class:`.Session`, and to continue using them, though this practice has its caveats. It's intended that -usually, you'd re-associate detached objects another :class:`.Session` when you +usually, you'd re-associate detached objects with another :class:`.Session` when you want to work with them again, so that they can resume their normal task of representing database state. |