delta/python-packages/sqlalchemy.git/lib/sqlalchemy/ext/associationproxy.py, branch rel_1_1

remote_attr and local_attr refer to class bound attributes, not MapperProperty

2019-04-25T22:24:42+00:00

backport from master

Change-Id: If3ffe0945f47010e1ddecabfc27a6e7707031fd9
(cherry picked from commit bcf2d5826ce8b1c68ee346154e86a4ecc9ac61c7)

Default to using current mapped class as owner if none found

2018-02-20T21:42:24+00:00

Repaired regression caused in 1.2.3 and 1.1.16 regarding association proxy
objects, revising the approach to :ticket:`4185` when calculating the
"owning class" of an association proxy to default to choosing the current
class if the proxy object is not directly associated with a mapped class,
such as a mixin.

Change-Id: I87d0ac09f695dc285bd4bbe0a547f1d5ce23e068
Fixes: #4185
(cherry picked from commit 93881f7873048403b62cc3e179354712ba8e9282)

Search through mapper superclass hierarchy for owner

2018-02-09T21:31:24+00:00

Fixed regression caused by fix for issue :ticket:`4116` affecting versions
1.2.2 as well as 1.1.15, which had the effect of mis-calculation of the
"owning class" of an :class:`.AssociationProxy` as the ``NoneType`` class
in some declarative mixin/inheritance situations as well as if the
association proxy were accessed off of an un-mapped class.  The "figure out
the owner" logic has been replaced by an in-depth routine that searches
through the complete mapper hierarchy assigned to the class or subclass to
determine the correct (we hope) match; will not assign the owner if no
match is found.  An exception is now raised if the proxy is used
against an un-mapped instance.

Change-Id: I611b590df2babe077ce6c19bea89e84251d1a7f4
Fixes: #4185
(cherry picked from commit 650b9eddae0eb198c8f8dc2d1e1e3c6ac53b18f3)

happy new year

2018-01-12T19:25:17+00:00

Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f
(cherry picked from commit 699272e4dcb9aa71ebbc0d9487fb6de82d3abc2b)

Resolve AliasedClass when determining owning class of association proxy

2017-10-24T00:36:18+00:00

Fixed bug where the association proxy would inadvertently link itself
to an :class:`.AliasedClass` object if it were called first with
the :class:`.AliasedClass` as a parent, causing errors upon subsequent
usage.

Change-Id: I9161bab67766bb75d73ca54d712ad1cad6de40dc
Fixes: #4116
(cherry picked from commit f14a58dea4b825beb4baaef44389880927543cc4)

Support python3.6

2017-01-13T15:57:41+00:00

Corrects some warnings and adds tox config.  Adds DeprecationWarning
to the error category.   Large sweep for string literals w/ backslashes
as this is common in docstrings

Co-authored-by: Andrii Soldatenko
Fixes: #3886
Change-Id: Ia7c838dfbbe70b262622ed0803d581edc736e085
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/337

update for 2017 copyright

2017-01-04T17:39:24+00:00

Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de

- happy new year

2016-01-29T16:20:22+00:00

Change generator termination from StopIteration to return.

2015-10-30T20:20:58+00:00

From [PEP 479](https://www.python.org/dev/peps/pep-0479/) the correct way to
terminate a generator is to return (which implicitly raises StopIteration)
rather than raise StopIteration.

Without this change using sqlalchemy in python 3.5 or greater results in
these warnings
    PendingDeprecationWarning: generator '__iter__' raised StopIteration
which this commit should remove.

- Added the :paramref:`.AssociationProxy.info` parameter to the

2015-10-09T22:01:43+00:00

:class:`.AssociationProxy` constructor, to suit the
:attr:`.AssociationProxy.info` accessor that was added in
:ticket:`2971`.  This is possible because :class:`.AssociationProxy`
is constructed explicitly, unlike a hybrid which is constructed
implicitly via the decorator syntax.
fixes #3551