From: Mike Bayer Date: Sun, 31 Jan 2010 15:49:51 +0000 (+0000) Subject: yikes entirely wrong option name here X-Git-Tag: rel_0_6beta1~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0421668763fc3b9d35043f0dc8d1613f81394cfc;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git yikes entirely wrong option name here --- diff --git a/doc/build/mappers.rst b/doc/build/mappers.rst index 4b0ff6f9f0..18ae039d9c 100644 --- a/doc/build/mappers.rst +++ b/doc/build/mappers.rst @@ -1766,7 +1766,7 @@ When ``passive_deletes`` is applied, the ``children`` relation will not be loade Mutable Primary Keys / Update Cascades --------------------------------------- -When the primary key of an entity changes, related items which reference the primary key must also be updated as well. For databases which enforce referential integrity, it's required to use the database's ON UPDATE CASCADE functionality in order to propagate primary key changes. For those which don't, the ``passive_cascades`` flag can be set to ``False`` which instructs SQLAlchemy to issue UPDATE statements individually. The ``passive_cascades`` flag can also be ``False`` in conjunction with ON UPDATE CASCADE functionality, although in that case it issues UPDATE statements unnecessarily. +When the primary key of an entity changes, related items which reference the primary key must also be updated as well. For databases which enforce referential integrity, it's required to use the database's ON UPDATE CASCADE functionality in order to propagate primary key changes. For those which don't, the ``passive_updates`` flag can be set to ``False`` which instructs SQLAlchemy to issue UPDATE statements individually. The ``passive_updates`` flag can also be ``False`` in conjunction with ON UPDATE CASCADE functionality, although in that case it issues UPDATE statements unnecessarily. A typical mutable primary key setup might look like: