delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/dependency.py, branch pr_github_383

Refinements for unitofwork internals

2017-06-14T16:54:53+00:00

* remove "mapper" argument from SaveUpdateState, DeleteState
* use __slots__ for all uow action classes
* rename ".delete" to ".isdelete"
* rename issue_post_update to register_post_update since this
  doesn't actually issue the UPDATE
* rename IssuePostUpdate to PostUpdateAll

Change-Id: Ia6263b80d6a86eab1e8ed38df1421b1d0f249797

update for 2017 copyright

2017-01-04T17:39:24+00:00

Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de

- happy new year

2016-01-29T16:20:22+00:00

- Fixed issue where post_update on a many-to-one relationship would

2015-12-02T17:13:57+00:00

fail to emit an UPDATE in the case where the attribute were set to
None and not previously loaded.
fixes #3599

- copyright 2015

2015-03-10T19:24:28+00:00

- restore non_updating_cascade to test_manytomany_nonpassive, but also

2014-07-25T22:51:44+00:00

add sane_multi_rowcount requirement, as pg8000 doesn't do "multi" row count.

- apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,

2014-07-20T16:44:40+00:00

sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing

- break up the copyright comment as part of a pass

2014-07-09T22:26:55+00:00

to get all flake8 passing

- Related to :ticket:`3060`, an adjustment has been made to the unit

2014-05-30T05:32:53+00:00

of work such that loading for related many-to-one objects is slightly
more aggressive, in the case of a graph of self-referential objects
that are to be deleted; the load of related objects is to help
determine the correct order for deletion if passive_deletes is
not set.
- revert the changes to test_delete_unloaded_m2o, these deletes do in fact
need to occur in the order of the two child objects first.

- Adjustment to attribute mechanics concerning when a value is

2014-05-29T23:54:51+00:00

implicitly initialized to None via first access; this action,
which has always resulted in a population of the attribute,
now emits an attribute event just like any other attribute set
operation and generates the same kind of history as one.  Additionally,
many mapper internal operations will no longer implicitly generate
these "None" values when various never-set attributes are checked.
These are subtle behavioral fixes to attribute mechanics which provide
a better solution to the problem of :ticket:`3060`, which also
involves recognition of attributes explicitly set to ``None``
vs. attributes that were never set.
fixes #3061