delta/python-packages/sqlalchemy.git/test/orm, branch pr/108

-do an autoflake8 here

2014-07-08T23:22:44+00:00

- The "evaulator" for query.update()/delete() won't work with multi-table

2014-07-08T23:08:42+00:00

updates, and needs to be set to `synchronize_session=False` or
`synchronize_session='fetch'`; this now raises an exception, with a
message to change the synchronize setting.  This will be only a warning
in 0.9.7.  fixes #3117

- ensure ACID set up on this table for MySQL

2014-07-01T19:28:16+00:00

- Fixed bug where items that were persisted, deleted, or had a

2014-07-01T16:12:51+00:00

primary key change within a savepoint block would not
participate in being restored to their former state (not in
session, in session, previous PK) after the outer transaction
were rolled back. fixes #3108

- repair the _enable_single_crit method, it was named the same

2014-07-01T00:25:04+00:00

as the attribute and probably just replaced itself, so that is
now _set_enable_single_crit
- as a side effect of the main issue fixed here, correct the case in
adjust_for_single_inheritance where the same mapper appears more
than once in mapper_adapter_map; run through a set() for uniqueness.
- Fixed bug in subquery eager loading in conjunction with
:func:`.with_polymorphic`, the targeting of entities and columns
in the subquery load has been made more accurate with respect
to this type of entity and others. Fixes #3106

- Fixed bug involving dynamic attributes, that was again a regression

2014-06-26T18:58:42+00:00

of :ticket:`3060` from verision 0.9.5.  A self-referential relationship
with lazy='dynamic' would raise a TypeError within a flush operation.
fixes #3099

- reverse course in #3061 so that we instead no longer set None in the attribute

2014-06-23T23:50:23+00:00

when we do a get; we return the None as always but we leave the dict blank
and the loader callable still in place.  The case for this implicit get on a pending object is not
super common and there really should be no change in state at all when this
operation proceeds.   This change is more dramatic as it reverses
a behavior SQLA has had since the first release.
fixes #3061

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

2014-06-23T22:42:54+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.

- use new Or() directive to test for both SQL variants here, which can vary

2014-06-22T00:27:19+00:00

based on hash ordering of the ClassManager

- Additional checks have been added for the case where an inheriting

2014-06-20T22:47:28+00:00

mapper is implicitly combining one of its column-based attributes
with that of the parent, where those columns normally don't necessarily
share the same value.  This is an extension of an existing check that
was added via :ticket:`1892`; however this new check emits only a
warning, instead of an exception, to allow for applications that may
be relying upon the existing behavior.
fixes #3042