delta/python-packages/sqlalchemy.git, branch pr/298

Clarify mappers.configure_mappers error message

2016-08-05T17:32:35+00:00

Sometimes the message generated by configure_mappers lacks a reference
to the failing mapper, and only the mapper._configure_failed is shown. This
makes debugging problems extremely difficult. Example:

    sqlalchemy.exc.InvalidRequestError: One or more mappers failed to
    initialize - can't proceed with initialization of other mappers.  Original
    exception was: Class 'neutron.objects.router.Router' is not mapped

In the above failure, the actual object having a problem is FloatingIP, which
has a knock-on effect on the Router object when it fails to map. A more helpful
error message might look like this example:

    sqlalchemy.exc.InvalidRequestError: One (Mapper|FloatingIp|floatingip) or
    more mappers failed to initialize - can't proceed with initialization of
    other mappers.  Original exception was: Class
    'neutron.objects.router.Router' is not mapped

This patch adds the failing mapper name to the beginning of the message after
'One', as shown in the second example.

Change-Id: I9f23bfa90b26dde9229ab7ec812eec9ceae48153

Build string/int processors for JSONIndexType, JSONPathType

2016-08-04T16:38:58+00:00

Fixed regression in JSON datatypes where the "literal processor" for
a JSON index value, that needs to take effect for example within DDL,
would not be invoked for the value.  The native String and Integer
datatypes are now called upon from within the JSONIndexType
and JSONPathType.  This is applied to the generic, Postgresql, and
MySQL JSON types.

Change-Id: Ifa5f2acfeee57a79d01d7fc85d265a37bd27c716
Fixes: #3765

Propagate kwargs to all MySQL CAST paths

2016-08-04T16:34:55+00:00

Change-Id: I23a6abb26bbbe3d118887d043ce761fc4572d8d2
Fixes: #3766

Warn that bulk save groups inserts/updates by type

2016-08-02T22:45:59+00:00

Users who pass many different object types to bulk_save_objects
may be surprised that the INSERT/UPDATE batches must necessarily
be broken up by type.  Add this to the list of caveats.

Co-authored-by: Mike Bayer
Change-Id: I8390c1c971ced50c41268b479a9dcd09c695b135
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/294

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

2016-08-02T22:34:05+00:00

Merge branch 'declarative-constructor-reference' of https://bitbucket.org/michaelwilliamson/sqlalchemy

2016-08-02T22:29:11+00:00

Ensure post-__clause_element__() expression are used in Index

2016-07-31T04:10:04+00:00

The change in Index for 1.1 combined with the fix for
ref #3763 still fails to deliver the correct object
resolved by __clause_element__() to the list of expressions
for compilation.   Make sure we use the expression that's
been unwrapped from __clause_element__().

Change-Id: Ie1df8db5090de665048331786f0024d52851923f
Fixes: #3763

Merge "Index should extract __clause_element__() early"

2016-07-30T16:54:10+00:00

Merge "Clarify order_by(False)"

2016-07-30T16:53:26+00:00

Index should extract __clause_element__() early

2016-07-30T14:11:53+00:00

Fixed bug where :class:`.Index` would fail to extract columns from
compound SQL expressions if those SQL expressions were wrapped inside
of an ORM-style ``__clause_element__()`` construct.  This bug
exists in 1.0.x as well, however in 1.1 is more noticeable as
hybrid_property @expression now returns a wrapped element.

Fixes: #3763

Change-Id: I992536386503a1fb3f2305790abe008d72c44c4a