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

Fix some typos in 1.1's changelog and migration sections

2016-07-02T11:07:48+00:00

Consistently use the official PostgreSQL casing

2016-07-02T11:05:27+00:00

- add backports

2016-07-01T18:59:18+00:00

Change-Id: Iee0bf9e60a5991bedbe29b305803b4c79ac5c511
(cherry picked from commit 849df799ec4107d0992c8eb0e015b74916aee266)

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

- 1.1.0b2

2016-07-01T14:47:20+00:00

- revert the RTD reqs workaround, we are self-hosting now

2016-07-01T14:39:05+00:00

Change-Id: Ie11361147d497c6eb6418cdc850ed277dfbd1de4

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

Make boolean processors consistent between Py/C; coerce to 1/0

2016-06-23T23:58:43+00:00

The processing performed by the :class:`.Boolean` datatype for backends
that only feature integer types has been made consistent between the
pure Python and C-extension versions, in that the C-extension version
will accept any integer value from the database as a boolean, not just
zero and one; additionally, non-boolean integer values being sent to
the database are coerced to exactly zero or one, instead of being
passed as the original integer value.

Change-Id: I01e647547fd7047bd549dd70e1fa202c51e8328b
Fixes: #3730