diff options
author | Vraj Mohan <r.vrajmohan@gmail.com> | 2013-11-15 08:41:00 -0500 |
---|---|---|
committer | Vraj Mohan <r.vrajmohan@gmail.com> | 2013-11-17 17:37:55 -0500 |
commit | 539922f00c79c0a05363972bbcf17d179cc9ecaa (patch) | |
tree | bc2166c44e5356e5831cf9e3bfb0c118cb140383 /lib/sqlalchemy/ext/mutable.py | |
parent | 1a809b300e0f77888e4cdac42f9e1662baa169c7 (diff) | |
download | sqlalchemy-539922f00c79c0a05363972bbcf17d179cc9ecaa.tar.gz |
Remove reference to defunct class
We should probably reword this entirely as, IMHO, this should be in the
changelog and not in the doc proper (which should only describe the
current state of affairs).
Diffstat (limited to 'lib/sqlalchemy/ext/mutable.py')
-rw-r--r-- | lib/sqlalchemy/ext/mutable.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/sqlalchemy/ext/mutable.py b/lib/sqlalchemy/ext/mutable.py index 5458de381..a83a2a19f 100644 --- a/lib/sqlalchemy/ext/mutable.py +++ b/lib/sqlalchemy/ext/mutable.py @@ -9,7 +9,7 @@ which are propagated into ORM change events on owning parent objects. The :mod:`sqlalchemy.ext.mutable` extension replaces SQLAlchemy's legacy approach to in-place mutations of scalar values, established by the -:class:`.types.MutableType` class as well as the ``mutable=True`` type flag, +``types.MutableType`` class as well as the ``mutable=True`` type flag, with a system that allows change events to be propagated from the value to the owning parent, thereby removing the need for the ORM to maintain copies of values as well as the very expensive requirement of scanning through all |