Log message:
SQLAlchemy release 1.1.12 is now available.

This release repairs an issue in the test suite that would prevent the suite \ 
from passing on Python version 3.6.2. The release is made at the same time as \ 
that of release 1.0.18 and 1.2.0b2. Also included are fixes related to ORM use \ 
of JSON NULL values, subquery eager loading, and a stability enhancement \ 
involving the identity map when used under high concurrency.

Log message:
1.1.11

orm

[orm] [bug] Fixed issue with subquery eagerloading which continues on from the \ 
series of issues fixed in 2699, 3106, 3893 involving that the \ 
“subquery” contains the correct FROM clause when beginning from a \ 
joined inheritance subclass and then subquery eager loading onto a relationship \ 
from the base class, while the query also includes criteria against the \ 
subclass. The fix in the previous tickets did not accommodate for additional \ 
subqueryload operations loading more deeply from the first level, so the fix has \ 
been further generalized.

sql

[sql] [bug] Fixed AttributeError which would occur in WithinGroup construct \ 
during an iteration of the structure.

postgresql

[postgresql] [bug] Continuing with the fix that correctly handles Postgresql \ 
version string “10devel” released in 1.1.8, an additional regexp bump \ 
to handle version strings of the form “10beta1”. While Postgresql now \ 
offers better ways to get this information, we are sticking w/ the regexp at \ 
least through 1.1.x for the least amount of risk to compatibility w/ older or \ 
alternate Postgresql databases.

[postgresql] [bug] Fixed bug where using ARRAY with a string type that features \ 
a collation would fail to produce the correct syntax within CREATE TABLE.

mysql

[mysql] [bug] MySQL 5.7 has introduced permission limiting for the “SHOW \ 
VARIABLES” command; the MySQL dialect will now handle when SHOW returns no \ 
row, in particular for the initial fetch of SQL_MODE, and will emit a warning \ 
that user permissions should be modified to allow the row to be present.

mssql

[mssql] [bug] Fixed bug where SQL Server transaction isolation must be fetched \ 
from a different view when using Azure data warehouse, the query is now \ 
attempted against both views and then a NotImplemented is raised unconditionally \ 
if failure continues to provide the best resiliency against future arbitrary API \ 
changes in new SQL Server versions.

[mssql] [bug] Added a placeholder type mssql.XML to the SQL Server dialect, so \ 
that a reflected table which includes this type can be re-rendered as a CREATE \ 
TABLE. The type has no special round-trip behavior nor does it currently support \ 
additional qualifying arguments.

oracle

[oracle] [bug] Support for two-phase transactions has been removed entirely for \ 
cx_Oracle when version 6.0b1 or later of the DBAPI is in use. The two- phase \ 
feature historically has never been usable under cx_Oracle 5.x in any case, and \ 
cx_Oracle 6.x has removed the connection-level “twophase” flag upon \ 
which this feature relied.

Log message:
Release 1.1.10 contains a short series of fixes to specific behaviors, primarily \ 
in Core, as well as one issue with "delete orphan" cascade when using \ 
inheriting mappers. No regressions were encountered since 1.1.9. Release 1.1.10 \ 
is recommended for users who are impacted by the specific issues listed.

Log message:
Reset MAINTAINER after tonnerre resigned.

Log message:
Changes 1.1.9:
A continuing stream of small regressions is leading us to have to put out \ 
releases every few days at the moment. This release includes a fix to a \ 
regression that was caused by a fix to a regression :), specifically the \ 
sqlalchemy.ext.mutable fix put out in 1.1.8. It also fixes a different \ 
regression in the typing system introduced in 1.1.5, and also has a regular bug \ 
fix for another issue regarding "connectionless" execution.

Log message:
Release 1.1.8 is only a few days past 1.1.7, however is being released early in \ 
order to deliver a few fixes requested by downstream projects. In particular, a \ 
regression from the 1.0.x series involving the sqlalchemy.ext.mutable extension \ 
is fixed.

Log message:
Release 1.1.7 includes several bugfixes, one of which was introduced in 1.1.6 as \ 
a result of performance enhancements for joined eager loading which presents as \ 
a race condition under certain multithreaded scenarios. Fixes also include an \ 
important adjustment in the cx_Oracle dialect to adjust for changes in cx_Oracle \ 
release 5.3, resolution of an extremely small memory leak which could occur in \ 
the relatively unusual case that an arbitrarily high number of savepoints were \ 
established on a single Connection object, as well as an important fix in the \ 
"schema translate" feature.

Log message:
Release 1.1.6 continues to provide bug fixes and some new features within the \ 
1.1 series. As we begin to lead into the development phase for 1.2 and solidify \ 
the 1.1 series as "done", additional behavioral improvements will more \ 
likely to be targeted at 1.2 rather than 1.1. Nevertheless, 1.1.6 includes a few \ 
fairly major behavioral improvements in the area of performance; some \ 
significant performance issues within the "joined eager loading" \ 
functionality were identified and repaired, which should cut the Python-level \ 
latency for such a query roughly in half, as well as an unnecessary SELECT which \ 
could emit when using the "eager defaults" feature was repaired.

Log message:
Release 1.1.5 has many bug fixes across the ORM and Core components as well as \ 
within the Postgresql, Mysql, Oracle, and SQL Server dialects. There is also one \ 
new feature allowing MySQL index prefixes to be specified.

Log message:
Release 1.0.15 features a small number of bug fixes that have been made over the \ 
past two months since the previous 1.0.x release.