delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/dynamic.py, branch rel_1_2 github.com: zzzeek/sqlalchemy.git happy new year 2019-01-11T15:07:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-11T15:06:10+00:00 3cfc3c2faaf6465fef75242a17961e4cfeee405b Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911 (cherry picked from commit 6f270fb0e344016ce526e0a1ecb3e3de9ffd1e3b) 
Change-Id: I6a71f4924d046cf306961c58dffccf21e9c03911
(cherry picked from commit 6f270fb0e344016ce526e0a1ecb3e3de9ffd1e3b)
Post black reformatting 2019-01-06T16:51:20+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:32:41+00:00 18abd47af32136b3c94a8a787905286d279181fa Applied on top of a pure run of black -l 79 in I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9, this set of changes resolves all remaining flake8 conditions for those codes we have enabled in setup.cfg. Included are resolutions for all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe 
Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe
Run black -l 79 against all source files 2019-01-06T06:31:01+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-01-06T06:31:01+00:00 580139598f846f1ce4e2bcfb522ec51d1829c580 This is a straight reformat run using black as is, with no edits applied at all. The black run will format code consistently, however in some cases that are prevalent in SQLAlchemy code it produces too-long lines. The too-long lines will be resolved in the following commit that will resolve all remaining flake8 issues including shadowed builtins, long lines, import order, unused imports, duplicate imports, and docstring issues. Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9 
This is a straight reformat run using black as is, with no edits
applied at all.

The black run will format code consistently, however in
some cases that are prevalent in SQLAlchemy code it produces
too-long lines.   The too-long lines will be resolved in the
following commit that will resolve all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9
Insert primary entity in dynamic "secondary" 2018-11-13T23:36:52+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-11-12T20:09:37+00:00 105d8d2fcaaf77ee2632d8f5ea959b8a3f6b7030 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) 
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)
Add prop.secondary to FROM for dynamic loader 2018-10-17T17:45:34+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-10-17T14:42:50+00:00 5311000cb390198afb9d96cf1aae17c713210b7b Fixed bug where "dynamic" loader needs to explicitly set the "secondary" table in the FROM clause of the query, to suit the case where the secondary is a join object that is otherwise not pulled into the query from its columns alone. Fixes: #4349 Change-Id: I397f62abd5603efa4fb273586d0f772bf8c8fbbf (cherry picked from commit d080aae128b081e6870dae325cb90202329784b4) 
Fixed bug where "dynamic" loader needs to explicitly set the "secondary"
table in the FROM clause of the query, to suit the case where the secondary
is a join object that is otherwise not pulled into the query from its
columns alone.

Fixes: #4349
Change-Id: I397f62abd5603efa4fb273586d0f772bf8c8fbbf
(cherry picked from commit d080aae128b081e6870dae325cb90202329784b4)
Ensure backrefs accommodate for op_bulk_replace 2018-01-25T01:55:13+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-01-24T16:09:47+00:00 4e2d825c63869a36aa3fbbca4550717a2e48e56f Fixed 1.2 regression regarding new bulk_replace event where a backref would fail to remove an object from the previous owner when a bulk-assignment assigned the object to a new owner. As this revisits the Event tokens associated with AttributeImpl objects, remove the verbosity of the "inline lazy init" pattern; the Event token is a simple slotted object and should have minimal memory overhead. Change-Id: Id188b4026fc2f3500186548008f4db8cdf7afecc Fixes: #4171 
Fixed 1.2 regression regarding new bulk_replace event
where a backref would fail to remove an object from the
previous owner when a bulk-assignment assigned the
object to a new owner.

As this revisits the Event tokens associated with
AttributeImpl objects, remove the verbosity of the
"inline lazy init" pattern; the Event token is a simple
slotted object and should have minimal memory overhead.

Change-Id: Id188b4026fc2f3500186548008f4db8cdf7afecc
Fixes: #4171
happy new year 2018-01-12T19:23:53+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-01-12T19:23:53+00:00 699272e4dcb9aa71ebbc0d9487fb6de82d3abc2b Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f 
Change-Id: I3ef36bfd0cb0ba62b3123c8cf92370a43156cf8f
Support state expiration for with_expression(); rename deferred_expression 2017-06-26T17:49:49+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-06-26T17:24:22+00:00 9ac0f8119e34a696fbf711e00262e9c0851b749c The attributeimpl for a deferred_expression does not support a scalar loader, add new configurability so that the impl can have this flag turned off. Document that the with_expression() system currently does not offer any deferred loading. To eliminate confusion over "deferred", which refers to lazy loading of column attributes, and "with_expression", which refers to an attribute that is explicitly at query time only, rename deferred_expression to query_expression. Change-Id: I07c4a050ed68c79ccbde9492e9de1630b7470d74 
The attributeimpl for a deferred_expression does not
support a scalar loader, add new configurability so that
the impl can have this flag turned off.   Document
that the with_expression() system currently does not
offer any deferred loading.

To eliminate confusion over "deferred", which refers to
lazy loading of column attributes, and "with_expression",
which refers to an attribute that is explicitly at
query time only, rename deferred_expression to query_expression.

Change-Id: I07c4a050ed68c79ccbde9492e9de1630b7470d74
update for 2017 copyright 2017-01-04T17:39:24+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-01-04T17:39:24+00:00 64e72b58fd74db0c5c87407c824d08ad699e5e8e Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de 
Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de
Move setup functionality into _register_attribute 2016-11-06T17:46:28+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-11-06T17:46:28+00:00 c4a8afa4c6bf5e76c24e8ed0b5c11acc0c8904e3 Options like uselist and backref can be determined from within _register_attribute based on parent_property given; move this logic inside so that individual strategies have less responsibility. Also don't require that _register_attribute consider the "strategy" itself at all; it would be better if we could no longer require that Joined/Subquery/etc loaders call upon the "lazy" strategy in order to initialize attribute instrumentation and this could be done more generically. Fixes long-standing bug where the "noload" relationship loading strategy would cause backrefs and/or back_populates options to be ignored. There is concern that some application that uses "noload" might be surprised at a back-populating attribute appearing suddenly, which may have side effects. However, "noload" itself must be extremely seldom used since as a strategy, it already disables loading, population of attributes is the only behavior that is even supported, so that this issue has existed for at least through 0.7 four years ago without ever being reported indicates extremely low use of this option. Change-Id: Icffb9c83ac5782b76ce882ed1df4361a1efbfba3 Fixes: #3845 
Options like uselist and backref can be determined from
within _register_attribute based on parent_property
given; move this logic inside so that individual strategies
have less responsibility.  Also don't require that
_register_attribute consider the "strategy" itself
at all; it would be better if we could no longer require
that Joined/Subquery/etc loaders call upon the "lazy" strategy
in order to initialize attribute instrumentation and
this could be done more generically.

Fixes long-standing bug where the "noload" relationship loading
strategy would cause backrefs and/or back_populates options to be
ignored.   There is concern that some application that uses
"noload" might be surprised at a back-populating attribute
appearing suddenly, which may have side effects.  However,
"noload" itself must be extremely seldom used since as a
strategy, it already disables loading, population of attributes
is the only behavior that is even supported, so that this issue has existed
for at least through 0.7 four years ago without ever being
reported indicates extremely low use of this option.

Change-Id: Icffb9c83ac5782b76ce882ed1df4361a1efbfba3
Fixes: #3845