Update sqlalchemy to 1.2.12

[pyup-bot]

This PR updates sqlalchemy from 1.2.10 to 1.2.12.

Changelog

1.2.12

:released: September 19, 2018

 .. change::
     :tags: bug, postgresql
     :tickets: 4325

     Fixed bug in PostgreSQL dialect where compiler keyword arguments such as
     ``literal_binds=True`` were not being propagated to a DISTINCT ON
     expression.

 .. change::
     :tags: bug, ext
     :tickets: 4328

     Fixed issue where :class:`.BakedQuery` did not include the specific query
     class used by the :class:`.Session` as part of the cache key, leading to
     incompatibilities when using custom query classes, in particular the
     :class:`.ShardedQuery` which has some different argument signatures.

 .. change::
     :tags: bug, postgresql
     :tickets: 4324

     Fixed the :func:`.postgresql.array_agg` function, which is a slightly
     altered version of the usual :func:`.functions.array_agg` function, to also
     accept an incoming "type" argument without forcing an ARRAY around it,
     essentially the same thing that was fixed for the generic function in 1.1
     in :ticket:`4107`.

 .. change::
     :tags: bug, postgresql
     :tickets: 4323

     Fixed bug in PostgreSQL ENUM reflection where a case-sensitive, quoted name
     would be reported by the query including quotes, which would not match a
     target column during table reflection as the quotes needed to be stripped
     off.


 .. change::
    :tags: bug, orm

    Added a check within the weakref cleanup for the :class:`.InstanceState`
    object to check for the presence of the ``dict`` builtin, in an effort to
    reduce error messages generated when these cleanups occur during interpreter
    shutdown.  Pull request courtesy Romuald Brunet.

 .. change::
     :tags: bug, orm, declarative
     :tickets: 4326

     Fixed bug where the declarative scan for attributes would receive the
     expression proxy delivered by a hybrid attribute at the class level, and
     not the hybrid attribute itself, when receiving the descriptor via the
     ``declared_attr`` callable on a subclass of an already-mapped class. This
     would lead to an attribute that did not report itself as a hybrid when
     viewed within :attr:`.Mapper.all_orm_descriptors`.


 .. change::
     :tags: bug, orm
     :tickets: 4334
     :versions: 1.3.0b1

     Fixed bug where use of :class:`.Lateral` construct in conjunction with
     :meth:`.Query.join` as well as :meth:`.Query.select_entity_from` would not
     apply clause adaption to the right side of the join.   "lateral" introduces
     the use case of the right side of a join being correlatable.  Previously,
     adaptation of this clause wasn't considered.   Note that in 1.2 only,
     a selectable introduced by :meth:`.Query.subquery` is still not adapted
     due to :ticket:`4304`; the selectable needs to be produced by the
     :func:`.select` function to be the right side of the "lateral" join.

 .. change::
    :tags: bug, oracle
    :tickets: 4335

    Fixed issue for cx_Oracle 7.0 where the behavior of Oracle param.getvalue()
    now returns a list, rather than a single scalar value, breaking
    autoincrement logic throughout the Core and ORM. The dml_ret_array_val
    compatibility flag is used for cx_Oracle 6.3 and 6.4 to establish compatible
    behavior with 7.0 and forward, for cx_Oracle 6.2.1 and prior a version
    number check falls back to the old logic.


 .. change::
     :tags: bug, orm
     :tickets: 4327

     Fixed 1.2 regression caused by :ticket:`3472` where the handling of an
     "updated_at" style column within the context of a post-update operation
     would also occur for a row that is to be deleted following the update,
     meaning both that a column with a Python-side value generator would show
     the now-deleted value that was emitted for the UPDATE before the DELETE
     (which was not the previous behavor), as well as that a SQL- emitted value
     generator would have the attribute expired, meaning the previous value
     would be unreachable due to the row having been deleted and the object
     detached from the session.The "postfetch" logic that was added as part of
     :ticket:`3472` is now skipped entirely for an object that ultimately is to
     be deleted.

.. changelog::

1.2.11

:released: August 20, 2018

 .. change::
     :tags: bug, py3k

     Started importing "collections" from "collections.abc" under Python 3.3 and
     greater for Python 3.8 compatibility.  Pull request courtesy Nathaniel
     Knight.

 .. change::
     :tag: bug, sqlite

     Fixed issue where the "schema" name used for a SQLite database within table
     reflection would not quote the schema name correctly.  Pull request
     courtesy Phillip Cloud.

 .. change::
     :tags: bug, sql
     :tickets: 4320

     Fixed issue that is closely related to :ticket:`3639` where an expression
     rendered in a boolean context on a non-native boolean backend would
     be compared to 1/0 even though it is already an implcitly boolean
     expression, when :meth:`.ColumnElement.self_group` were used.  While this
     does not affect the user-friendly backends (MySQL, SQLite) it was not
     handled by Oracle (and possibly SQL Server).   Whether or not the
     expression is implicitly boolean on any database is now determined
     up front as an additional check to not generate the integer comparison
     within the compliation of the statement.

 .. change::
     :tags: bug, oracle
     :tickets: 4309

     For cx_Oracle, Integer datatypes will now be bound to "int", per advice
     from the cx_Oracle developers.  Previously, using cx_Oracle.NUMBER caused a
     loss in precision within the cx_Oracle 6.x series.


 .. change::
     :tags: bug, orm, declarative
     :tickets: 4321

     Fixed issue in previously untested use case, allowing a declarative mapped
     class to inherit from a classically-mapped class outside of the declarative
     base, including that it accommodates for unmapped intermediate classes. An
     unmapped intermediate class may specify ``__abstract__``, which is now
     interpreted correctly, or the intermediate class can remain unmarked, and
     the classically mapped base class will be detected within the hierarchy
     regardless. In order to anticipate existing scenarios which may be mixing
     in classical mappings into existing declarative hierarchies, an error is
     now raised if multiple mapped bases are detected for a given class.

 .. change::
     :tags: bug, sql
     :tickets: 4322

     Added missing window function parameters
     :paramref:`.WithinGroup.over.range_` and :paramref:`.WithinGroup.over.rows`
     parameters to the :meth:`.WithinGroup.over` and
     :meth:`.FunctionFilter.over` methods, to correspond to the range/rows
     feature added to the "over" method of SQL functions as part of
     :ticket:`3049` in version 1.1.

 .. change::
     :tags: bug, sql
     :tickets: 4313

     Fixed bug where the multi-table support for UPDATE and DELETE statements
     did not consider the additional FROM elements as targets for correlation,
     when a correlated SELECT were also combined with the statement.  This
     change now includes that a SELECT statement in the WHERE clause for such a
     statement will try to auto-correlate back to these additional tables in the
     parent UPDATE/DELETE or unconditionally correlate if
     :meth:`.Select.correlate` is used.  Note that auto-correlation raises an
     error if the SELECT statement would have no FROM clauses as a result, which
     can now occur if the parent UPDATE/DELETE specifies the same tables in its
     additional set of tables; specify :meth:`.Select.correlate` explicitly to
     resolve.

.. changelog::

Links

• PyPI: https://pypi.org/project/sqlalchemy
• Changelog: https://pyup.io/changelogs/sqlalchemy/
• Homepage: http://www.sqlalchemy.org

[coveralls]

Coverage remained the same at 33.933% when pulling bee36c5 on pyup-update-sqlalchemy-1.2.10-to-1.2.12 into aa4fbb8 on master.

[pyup-bot]

Closing this in favor of #311