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

Deprecate Mapper.order_by

2016-04-19T22:17:45+00:00

This is an old parameter no longer relevant to how SQLAlchemy
works, once the Query object was introduced.  By deprecating it
we establish that we aren't supporting non-working use cases
and that we encourage applications to move off of the use of this
parameter.

Fixes: #3394
Change-Id: I25b9a38142a1537bbcb27d3e8b66a8b265140072

- skip GC tests here when coverage is enabled, seems to interfere

2016-03-08T14:28:44+00:00

- An improvement to the workings of :meth:`.Query.correlate` such

2016-02-26T04:27:49+00:00

that when a "polymorphic" entity is used which represents a straight
join of several tables, the statement will ensure that all the
tables within the join are part of what's correlating.
fixes #3662

- use regex here, columns dont matter, keep coming up with different orderings

2016-01-23T20:32:10+00:00

- make this test deterministic

2016-01-21T22:20:52+00:00

- Added new parameter :paramref:`.orm.mapper.passive_deletes` to

2016-01-20T22:59:56+00:00

available mapper options.   This allows a DELETE to proceed
for a joined-table inheritance mapping against the base table only,
while allowing for ON DELETE CASCADE to handle deleting the row
from the subclass tables.
fixes #2349

- Fixed issue where two same-named relationships that refer to

2016-01-19T18:34:42+00:00

a base class and a concrete-inherited subclass would raise an error
if those relationships were set up using "backref", while setting up the
identical configuration using relationship() instead with the conflicting
names would succeed, as is allowed in the case of a concrete mapping.
fixes #3630

- varchar requires a length

2015-12-22T16:19:44+00:00

- add the test from ref #3614 as well for testing ref #3611

2015-12-22T02:42:45+00:00

- Fixed regression caused in 1.0.10 by the fix for :ticket:`3593` where

2015-12-15T19:00:50+00:00

the check added for a polymorphic joinedload from a
poly_subclass->class->poly_baseclass connection would fail for the
scenario of class->poly_subclass->class.
fixes #3611