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

- copyright 2015

2015-03-10T19:27:20+00:00

- restore non_updating_cascade to test_manytomany_nonpassive, but also

2014-07-25T22:52:25+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-20T17:11:41+00:00

sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing

Conflicts:
	lib/sqlalchemy/dialects/mssql/base.py
	lib/sqlalchemy/dialects/mysql/base.py
	lib/sqlalchemy/dialects/mysql/mysqldb.py
	lib/sqlalchemy/dialects/oracle/base.py
	lib/sqlalchemy/dialects/sybase/base.py
	lib/sqlalchemy/orm/attributes.py
	lib/sqlalchemy/orm/evaluator.py
	lib/sqlalchemy/orm/identity.py
	lib/sqlalchemy/orm/instrumentation.py
	lib/sqlalchemy/orm/loading.py
	lib/sqlalchemy/orm/mapper.py
	lib/sqlalchemy/orm/session.py
	lib/sqlalchemy/orm/sync.py
	lib/sqlalchemy/sql/compiler.py
	lib/sqlalchemy/sql/selectable.py
	lib/sqlalchemy/testing/requirements.py
	lib/sqlalchemy/testing/suite/test_select.py

- break up the copyright comment as part of a pass

2014-07-09T22:29:17+00:00

  to get all flake8 passing

- Reverted the change for :ticket:`3060` - this is a unit of work

2014-06-23T22:38:23+00:00

fix that is updated more comprehensively in 1.0 via :ticket:`3061`.
The fix in :ticket:`3060` unfortunately produces a new issue whereby
an eager load of a many-to-one attribute can produce an event
that is interpreted into an attribute change.

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

2014-05-30T05:39:45+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.

merged from master

- Fixed a few edge cases which arise in the so-called "row switch"

2014-05-29T00:01:49+00:00

scenario, where an INSERT/DELETE can be turned into an UPDATE.
In this situation, a many-to-one relationship set to None, or
in some cases a scalar attribute set to None, may not be detected
as a net change in value, and therefore the UPDATE would not reset
what was on the previous row.   This is due to some as-yet
unresovled side effects of the way attribute history works in terms
of implicitly assuming None isn't really a "change" for a previously
un-set attribute.  See also :ticket:`3061`. fixes #3060

- happy new year

2014-01-05T21:57:05+00:00

Fixed bug where many-to-many relationship with uselist=False

2013-04-21T15:31:29+00:00

would fail to delete the association row and raise an error
if the scalar attribute were set to None.  Also in 0.7.11.
[ticket:2710]

happy new year (see #2645)

2013-01-01T18:46:21+00:00