class DetectKeySwitch(DependencyProcessor): (source)
For many-to-one relationships with no one-to-many backref, searches for parents through the unit of work when a primary key has changed and updates them. Theoretically, this approach could be expanded to support transparent deletion of objects referenced via many-to-one as well, although the current attribute system doesn't do enough bookkeeping for this to be efficient.
Method | per |
Undocumented |
Method | per |
establish actions and dependencies related to a flush. |
Method | per |
establish actions and dependencies related to a flush. |
Method | presort |
Undocumented |
Method | presort |
Undocumented |
Method | process |
Undocumented |
Method | process |
Undocumented |
Method | prop |
Undocumented |
Method | _key |
Undocumented |
Method | _pks |
Undocumented |
Method | _process |
Undocumented |
Inherited from DependencyProcessor
:
Class Method | from |
Undocumented |
Method | __init__ |
Undocumented |
Method | __repr__ |
Undocumented |
Method | hasparent |
return True if the given object instance has a parent, according to the ``InstrumentedAttribute`` handled by this ``DependencyProcessor``. |
Instance Variable | cascade |
Undocumented |
Instance Variable | direction |
Undocumented |
Instance Variable | enable |
Undocumented |
Instance Variable | key |
Undocumented |
Instance Variable | mapper |
Undocumented |
Instance Variable | parent |
Undocumented |
Instance Variable | passive |
Undocumented |
Instance Variable | passive |
Undocumented |
Instance Variable | post |
Undocumented |
Instance Variable | prop |
Undocumented |
Instance Variable | secondary |
Undocumented |
Instance Variable | sort |
Undocumented |
Method | _get |
Undocumented |
Method | _post |
Undocumented |
Method | _synchronize |
Undocumented |
Method | _verify |
Undocumented |
Instance Variable | _passive |
Undocumented |
Instance Variable | _passive |
Undocumented |
establish actions and dependencies related to a flush. These actions will operate on all relevant states in the aggregate.
establish actions and dependencies related to a flush. These actions will operate on all relevant states individually. This occurs only if there are cycles in the 'aggregated' version of events.