delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch pr/289

- fix typo

2016-07-07T20:07:21+00:00

Change-Id: Ie66d419a5188529a64fcb2e2463c15c26863889f

Merge "Adapt "FOR UPDATE OF" with Oracle limit/offset"

2016-07-06T14:13:56+00:00

Adapt "FOR UPDATE OF" with Oracle limit/offset

2016-07-05T22:30:25+00:00

This modifies the Oracle ROWNUM limit/offset approach
to accommodate for the "OF" clause in a "FOR UPDATE"
phrase.  The column expressions must be added to the selected
subquery if necessary and adapted on the outside.

Change-Id: Ia71b5fc4df6d326e73863f8ae9f96e8f1a5acfc1
Fixes: #3741

`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

- version bump

2016-07-05T17:05:07+00:00

Change-Id: I5ace1a90f36678c006d704b452fbbe8a3eb1cd0a

Repair PG BIGSERIAL w/ TypeDecorator, Variant

2016-07-04T20:54:01+00:00

Some of the dialect impl memoization for TypeDecorator
necessarily keeps the top-level TypeDecorator type
around, since a user-defined type will have bind and result
set processing behavior.  For both TypeDecorator and Variant,
PG dialect needs to ensure it's looking at the SQLAlchemy
type to check for SmallInteger / BigInteger.

Fixes: 3739
Change-Id: I2d45fb997f17c6272d6bb826a77d2dba665adae7
(cherry picked from commit 421fa6b8bf9f0c3c5041579c89ec405ce0f5e0b0)

Preserve type for math negation

2016-07-01T16:44:47+00:00

Fixed issue in SQL math negation operator where the type of the
expression would no longer be the numeric type of the original.
This would cause issues where the type determined result set
behaviors.

Change-Id: If0e339614a3686e251235fc94b6f59310c4630a5
Fixes: #3735

Merge "Repair pickling for Properties object"

2016-06-29T21:41:03+00:00

Repair pickling for Properties object

2016-06-29T21:21:31+00:00

Fixed bug whereby the ``__getstate__`` / ``__setstate__``
methods for sqlalchemy.util.Properties were
non-working due to the transition in the 1.0 series to ``__slots__``.
The issue potentially impacted some third-party applications.
Pull request courtesy Pieter Mulder.

Fixes: #3728
Change-Id: I01ebd425bbfe145747fea2edd0d2d412c74fd84d
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/286
(cherry picked from commit cab57e9bab04fbdea44690c08dff379a29eaab32)

Ensure @compiles calls down to the original compilation scheme

2016-06-29T15:14:28+00:00

Made a slight behavioral change in the ``sqlalchemy.ext.compiler``
extension, whereby the existing compilation schemes for an established
construct would be removed if that construct was itself didn't already
have its own dedicated ``__visit_name__``.  This was a
rare occurrence in 1.0, however in 1.1 :class:`.postgresql.ARRAY`
subclasses :class:`.sqltypes.ARRAY` and has this behavior.
As a result, setting up a compilation handler for another dialect
such as SQLite would render the main :class:`.postgresql.ARRAY`
object no longer compilable.

Fixes: #3732
Change-Id: If2c1ada4eeb09157885888e41f529173902f2b49