delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/strategies.py, branch pr_github_286

Merge remote-tracking branch 'origin/pr/270'

2016-05-24T20:29:49+00:00

Check for duplicate calls to register_attribute_impl

2016-05-10T15:05:30+00:00

Fixed bug whereby the event listeners used for backrefs could
be inadvertently applied multiple times, when using a deep class
inheritance hierarchy in conjunction with mutiple mapper configuration
steps.

Change-Id: I712beaf4674e2323bf5b282922658020a6d00b53
Fixes: #3710

Spelling fixes: "the a"

2016-05-05T06:00:28+00:00

Add raise/raiseload relationship loading strategy

2016-04-19T17:04:41+00:00

Fixes: #3512
Co-Authored-By: Mike Bayer 
Change-Id: Ibd126c50eda621e2f4120ee378f7313af2d7ec3c
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/193

- reworked the way the "select_wraps_for" expression is

2016-02-21T01:22:38+00:00

handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement.  The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe.  fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.

- Fixed bug which would cause an eagerly loaded many-to-one attribute

2016-02-17T23:01:20+00:00

to not be loaded, if the joined eager load were from a row where the
same entity were present multiple times, some calling for the attribute
to be eagerly loaded and others not.  The logic here is revised to
take in the attribute even though a different loader path has
handled the parent entity already. fixes #3431

- happy new year

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

- Fixed regression since 0.9 where the 0.9 style loader options

2016-01-09T15:10:20+00:00

system failed to accommodate for multiple :func:`.undefer_group`
loader options in a single query.   Multiple :func:`.undefer_group`
options will now be taken into account even against the same
entity. fixes #3623

- 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

- Fixed bug which is actually a regression that occurred between

2015-11-25T20:29:04+00:00

versions 0.8.0 and 0.8.1, due :ticket:`2714`.  The case where
joined eager loading needs to join out over a subclass-bound
relationship when "with_polymorphic" were also used would fail
to join from the correct entity.
fixes #3593