diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2016-08-02 18:34:05 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2016-08-02 18:34:05 -0400 |
| commit | 2dfa954e1f6af20f3104ef05ba126b37f8f4e5c5 (patch) | |
| tree | 7ddd392cf364dc5cb57f09d7ca8dcbef4e957dfa | |
| parent | a95c58df3bad05eb9580521ce466ff4ba23e9fad (diff) | |
| parent | 4aad91f687e905ef58132ab21af1ae60e56a9c8c (diff) | |
| download | sqlalchemy-2dfa954e1f6af20f3104ef05ba126b37f8f4e5c5.tar.gz | |
Merge remote-tracking branch 'origin/pr/296'
| -rw-r--r-- | doc/build/faq/sessions.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/faq/sessions.rst b/doc/build/faq/sessions.rst index ee280ae98..f7247aa21 100644 --- a/doc/build/faq/sessions.rst +++ b/doc/build/faq/sessions.rst @@ -321,7 +321,7 @@ how do I use ON DELETE CASCADE with SA's ORM? SQLAlchemy will always issue UPDATE or DELETE statements for dependent rows which are currently loaded in the :class:`.Session`. For rows which are not loaded, it will by default issue SELECT statements to load -those rows and udpate/delete those as well; in other words it assumes +those rows and update/delete those as well; in other words it assumes there is no ON DELETE CASCADE configured. To configure SQLAlchemy to cooperate with ON DELETE CASCADE, see :ref:`passive_deletes`. |