delta/python-packages/sqlalchemy.git/test/ext, branch pr/320

Assemble "don't joinedload other side" rule using query._current_path

2016-10-17T15:28:36+00:00

Discovered during testing for [ticket:3822], the rule added
for [ticket:1495] will fail if the source object has propagated
options set up, which add elements to query._current_path.

Fixes: #3824
Change-Id: I3d96c96fee5f9b247f739d2136d18681ac61f2fe

Enhance "raise" strategy to include "raise_on_sql" option

2016-10-04T16:09:29+00:00

The "raise_on_sql" option differentiates from "raise" in that
firing a lazy loader is OK as long as it does a simple
get from identity map.   Whereas "raise" is more useful
for the case that objects are to be detached.

As part of this, refactors the strategy initiation logic
a bit so that a LoaderStrategy itself knows what "key" was used
to create it, thus allowing variants of a single strategy
based on what the "lazy" argument is.  To achieve this we
have to also get rid of _get_strategy_by_cls().

Everything here is internal with the one exception of an apparently
undocumented, but not underscored, "strategy_class" key
on relationship().   Though it's not clear what
"strategy_class" accomplishes; at this point the strategy
system is extensible using Property.strategy_for().

Fixes: #3812
Change-Id: I812ad878ea5cf764e15f6f71cb39eee78a645d88

Add the "triggering mapper" to the configure_mappers error message.

2016-09-20T16:11:11+00:00

There are cases where the originating mapper name is not
present in the exception message, such as relationship initialization
against an unmapped class.   Ensure the originating mapper is named
in the string output.

Pull-request: https://github.com/zzzeek/sqlalchemy/pull/298
Change-Id: I9f23bfa90b26dde9229ab7ec812eec9ceae48153

Repair foreign_keys population for Join._refresh_for_new_column

2016-09-15T04:54:15+00:00

Fixed bug where setting up a single-table inh subclass of a joined-table
subclass which included an extra column would corrupt the foreign keys
collection of the mapped table, thereby interfering with the
initialization of relationships.

Change-Id: I04a0cf98fd456d12d5a5b9e77a46a01246969a63
Fixes: #3797

Add docstring to declarative_base

2016-08-06T01:25:27+00:00

Change-Id: I5ad44362515908592f1e8b1e6254a5270d43234a
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/295

- a variety of test adjustments to accomodate for MySQL 5.7

2016-07-24T20:36:27+00:00

Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387

Merge "Add `default` parameter for `index_property`"

2016-07-13T18:10:00+00:00

Fix issue with unbaking subqueries

2016-07-12T18:09:14+00:00

Fix improper capture of a loop variable inside a lambda during unbaking
of subquery eager loaders, which would cause the incorrect query
to be invoked.

Fixes: #3743
Change-Id: I995110deb8ee2dae8540486729e1ae64578d28fc
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/290

Add `default` parameter for `index_property`

2016-07-10T17:57:51+00:00

And force to use keyword arguments for trivial parameters in index_property

Change-Id: I12a178128182f77a2d06b52d7e36f59a36b45a33

`index_property` catches IndexError as well as KeyError

2016-07-05T22:24:47+00:00

It was raising AttributeError for key accessing in dict,
but raising IndexError for index accessing in array.

Change-Id: I58a2252a9e8d7f78cabcefcbe7223a4f3a729115