delta/python-packages/sqlalchemy.git/test/orm/test_subquery_relations.py, 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

- 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 in subquery eager loading where a long chain of

2014-05-25T17:45:32+00:00

eager loads across a polymorphic-subclass boundary in conjunction
with polymorphic loading would fail to locate the subclass-link in the
chain, erroring out with a missing property name on an
:class:`.AliasedClass`. fixes #3055

- Fixed a few errant ``u''`` strings that would prevent tests from passing

2014-03-22T22:48:59+00:00

in Py3.2.  Patch courtesy Arfrever Frehtes Taifersar Arahesis. fixes #2980

autoincrement here

2013-12-17T21:28:43+00:00

- An adjustment to the :func:`.subqueryload` strategy which ensures that

2013-12-17T00:17:41+00:00

the query runs after the loading process has begun; this is so that
the subqueryload takes precedence over other loaders that may be
hitting the same attribute due to other eager/noload situations
at the wrong time. [ticket:2887]

- remove informix dialect, moved out to https://bitbucket.org/zzzeek/sqlalchemy_informixdb

2013-11-17T18:45:23+00:00

- remove informix, maxdb, access symbols from tests etc.

use a set here also

2013-10-18T23:03:21+00:00

- fix non-deterministic ordering point

2013-10-14T14:35:54+00:00

- Added new option to :func:`.relationship` ``distinct_target_key``.

2013-10-13T20:42:32+00:00

This enables the subquery eager loader strategy to apply a DISTINCT
to the innermost SELECT subquery, to assist in the case where
duplicate rows are generated by the innermost query which corresponds
to this relationship (there's not yet a general solution to the issue
of dupe rows within subquery eager loading, however, when joins outside
of the innermost subquery produce dupes).  When the flag
is set to ``True``, the DISTINCT is rendered unconditionally, and when
it is set to ``None``, DISTINCT is rendered if the innermost relationship
targets columns that do not comprise a full primary key.
The option defaults to False in 0.8 (e.g. off by default in all cases),
None in 0.9 (e.g. automatic by default).   Thanks to Alexander Koval
for help with this. [ticket:2836]