summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Widman <jeff@jeffwidman.com>2016-07-25 19:07:19 -0700
committerGitHub <noreply@github.com>2016-07-25 19:07:19 -0700
commit4aad91f687e905ef58132ab21af1ae60e56a9c8c (patch)
tree50b59e52848cffebd93fb025e28dd99e050d4935
parent96c4208bf83607120d2f716070ed22ee10312dd0 (diff)
downloadsqlalchemy-pr/296.tar.gz
Fix typopr/296
-rw-r--r--doc/build/faq/sessions.rst2
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`.