delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/unitofwork.py, branch pr/264

- Fixed bug where a newly inserted instance that is rolled back

2016-03-14T21:56:57+00:00

would still potentially cause persistence conflicts on the next
transaction, because the instance would not be checked that it
was expired.   This fix will resolve a large class of cases that
erronously cause the "New instance with identity X conflicts with
persistent instance Y" error.
fixes #3677

- happy new year

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

- copyright 2015

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

- refinements

2014-08-19T18:24:56+00:00

- change to be represented as two very fast bulk_insert() and bulk_update() methods

2014-08-15T19:53:38+00:00

dev

2014-08-15T19:53:12+00:00

- proof of concept

2014-08-15T19:52:35+00:00

- 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.