delta/python-packages/sqlalchemy.git/test/orm/test_loading.py, branch pr/273 github.com: zzzeek/sqlalchemy.git - reworked the way the "select_wraps_for" expression is 2016-02-21T01:22:38+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-02-21T01:22:38+00:00 8ad968f33100baeb3b13c7e0b724b6b79ab4277f 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. 
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 where if an exception were thrown at the start of a 2015-01-06T02:38:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-01-06T02:38:19+00:00 57f684b4b4a661c78de0b5953603984714f01e0b :class:`.Query` before it fetched results, particularly when row processors can't be formed, the cursor would stay open with results pending and not actually be closed. This is typically only an issue on an interpreter like Pypy where the cursor isn't immediately GC'ed, and can in some circumstances lead to transactions/ locks being open longer than is desirable. fixes #3285 
:class:`.Query` before it fetched results, particularly when
row processors can't be formed, the cursor would stay open with
results pending and not actually be closed.  This is typically only
an issue on an interpreter like Pypy where the cursor isn't
immediately GC'ed, and can in some circumstances lead to transactions/
locks being open longer than is desirable.
fixes #3285
- the raw 2to3 run 2013-04-27T23:53:57+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-04-27T23:53:57+00:00 4b614b9b35cd2baddb7ca67c04bee5d70ec6a172 - went through examples/ and cleaned out excess list() calls 
- went through examples/ and cleaned out excess list() calls
:meth:`.Query.merge_result` can now load rows from an outer join 2013-01-08T15:55:46+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-01-08T15:55:46+00:00 06ddce3215d771e3345e19c5d3a1857b23db69f1 where an entity may be ``None`` without throwing an error. [ticket:2640] 
where an entity may be ``None`` without throwing an error.
[ticket:2640]
- add coverage for merge_result() [ticket:2588] 2012-10-11T20:59:02+00:00 Mike Bayer mike_mp@zzzcomputing.com 2012-10-11T20:59:02+00:00 78313a1ae33f6937b9f1ab90270fb8c0b0fb91ff - pre-determine keys for the keyed tuples 
- pre-determine keys for the keyed tuples