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

- flake8 refactor - test_orm

2019-01-05T23:00:06+00:00

A full rewrite of all imports and pep8 formatting using zimports, black,
commits are broken into sections.

Directories included in this commit:

    test/orm/ test/ext/

did not fully merge this one, needs to be done from scratch

Change-Id: I22b42d81bbc35c3a4a8ad4e48dbc78c363cdd4e3
(cherry picked from commit 380f75c051314e615694cdb9186e8ac7de128131)

partial cherry-pick of master flake8. clean cherrypick for lib and test,

2019-01-05T17:53:38+00:00

manually merged exaples.

Change-Id: I9532d3b13d13f2769e6ca48eea23dd7d4041f68f
(cherry picked from commit e3bdd80c6661c0e95fb67998c57540be667ce761)

zimports for all of test/

2019-01-05T17:13:02+00:00

step 1, straight black -l 79 run

2019-01-05T17:06:50+00:00

includes adjustment to setup.py to recognize __version__ correctly

Document and support nested composites

2018-12-12T17:54:56+00:00

Composites can behave in a "nested" fashion by defining the
class in that way.   To make the constructor more convenient,
a callable can be passed to :func:`.composite` instead of the
class itself.  This works now, so add a test to ensure this
pattern remains available.

Change-Id: Ia009f274fca7269f41d6d824e0f70b6fb0ada081
(cherry picked from commit d4a130bb1b92869efe33675262c7b1fde364e477)

Refer to existing of_type when resolving string attribute name

2018-12-07T21:04:24+00:00

Fixed bug where chaining of mapper options using
:meth:`.RelationshipProperty.of_type` in conjunction with a chained option
that refers to an attribute name by string only would fail to locate the
attribute.

Fixes: #4400
Change-Id: I01bf449ec4d8f56bb8c34e25153c1c9b31ff8012
(cherry picked from commit 099f3fd812ff4424f90f3c2b41ddce7049a54022)

Add secondary selectable to FROM clauses for correlated exists

2018-11-14T22:37:55+00:00

In continuing with a similar theme as that of very recent :ticket:`4349`,
repaired issue with :meth:`.RelationshipProperty.Comparator.any` and
:meth:`.RelationshipProperty.Comparator.has` where the "secondary"
selectable needs to be explicitly part of the FROM clause in the
EXISTS subquery to suit the case where this "secondary" is a :class:`.Join`
object.

Fixes: #4366
Change-Id: Icd0d0c3871bbd0059f0c9256e2b980edc2c90551
(cherry picked from commit fdfd1680603f6663182ba4766ae2f5abdd3ced45)

Merge "Deannotate "parententity" in primaryjoin/secondaryjoin" into rel_1_2

2018-11-14T19:22:36+00:00

Deannotate "parententity" in primaryjoin/secondaryjoin

2018-11-14T16:37:20+00:00

Fixed bug where the ORM annotations could be incorrect for the
primaryjoin/secondaryjoin a relationship if one used the pattern
``ForeignKey(SomeClass.id)`` in the declarative mappings.   This pattern
would leak undesired annotations into the join conditions which can break
aliasing operations done within :class:`.Query` that are not supposed to
impact elements in that join condition.  These annotations are now removed
up front if present.

Also add a test suite for has/any into test_query which will
form the basis for new tests to be added in :ticket:`4366`.

Fixes: #4367
Change-Id: I929ef983981bb49bf975f346950ebb0e19c986b8
(cherry picked from commit 4ee5b2c4a9e7ad9f3df75940b9837d5c65cba6fd)

Insert primary entity in dynamic "secondary"

2018-11-13T23:36:52+00:00

Fixed regression caused by :ticket:`4349` where adding the "secondary"
table to the FROM clause for a dynamic loader would affect the ability of
the :class:`.Query` to make a subsequent join to another entity.   The fix
adds the primary entity as the first element of the FROM list since
:meth:`.Query.join` wants to jump from that.   Version 1.3 will have
a more comprehensive solution to this problem as well (:ticket:`4365`).

Fixes: #4363
Change-Id: I1abbb6207722619dc5369e1fd96de43d60a1ee62
(cherry picked from commit 40c1a46e993b5c5ff917ce41c3dca66c139bde94)