Apparently, readthedocs has been not building for over a week, so at the
moment the CHANGES link below is very stale. We are trying to get RTD
to respond for help.
In the meantime, here's a paste of the changelog for 1.0.13:
1.0.13
Released: May 16, 2016
orm
[orm] [bug] Fixed bug in “evaluate” strategy of Query.update() and
Query.delete() which would fail to accommodate a bound parameter with a
“callable” value, as which occurs when filtering by a many-to-one
equality expression along a relationship.
References: #3700
[orm] [bug] Fixed bug whereby the event listeners used for backrefs
could be inadvertently applied multiple times, when using a deep class
inheritance hierarchy in conjunction with mutiple mapper configuration
steps.
References: #3710
[orm] [bug] Fixed bug whereby passing a text() construct to the
Query.group_by() method would raise an error, instead of intepreting the
object as a SQL fragment.
References: #3706
[orm] [bug] Anonymous labeling is applied to a func construct that
is passed to column_property(), so that if the same attribute is
referred to as a column expression twice the names are de-duped, thus
avoiding “ambiguous column” errors. Previously, the .label(None) would
need to be applied in order for the name to be de-anonymized.
References: #3663
[orm] [bug] Fixed regression appearing in the 1.0 series in ORM
loading where the exception raised for an expected column missing would
incorrectly be a NoneType error, rather than the expected NoSuchColumnError.
References: #3658
sql
[sql] [bug] Fixed bug where when using case_sensitive=False with an
Engine, the result set would fail to correctly accomodate for duplicate
column names in the result set, causing an error when the statement is
executed in 1.0, and preventing the “ambiguous column” exception from
functioning in 1.1.
References: #3690
[sql] [bug] Fixed bug where the negation of an EXISTS expression
would not be properly typed as boolean in the result, and also would
fail to be anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
References: #3682
[sql] [bug] Fixed bug where “unconsumed column names” exception
would fail to be raised in the case where Insert.values() were called
with a list of parameter mappings, instead of a single mapping of
parameters. Pull request courtesy Athena Yao.
References: #3666
postgresql
[postgresql] [bug] Added disconnect detection support for the error
string “SSL error: decryption failed or bad record mac”. Pull request
courtesy Iuri de Silvio.
References: #3715
mssql
[mssql] [bug] Fixed bug where by ROW_NUMBER OVER clause applied for
OFFSET selects in SQL Server would inappropriately substitute a plain
column from the local statement that overlaps with a label name used by
the ORDER BY criteria of the statement.
References: #3711
[mssql] [bug] [oracle] Fixed regression appearing in the 1.0 series
which would cause the Oracle and SQL Server dialects to incorrectly
account for result set columns when these dialects would wrap a SELECT
in a subquery in order to provide LIMIT/OFFSET behavior, and the
original SELECT statement referred to the same column multiple times,
such as a column and a label of that same column. This issue is related
to #3658 in that when the error occurred, it would also cause a NoneType
error, rather than reporting that it couldn’t locate a column.
References: #3657
oracle
[oracle] [bug] Fixed a bug in the cx_Oracle connect process that
caused a TypeError when the either the user, password or dsn was empty.
This prevented external authentication to Oracle databases, and
prevented connecting to the default dsn. The connect string oracle://
now logs into the default dsn using the Operating System username,
equivalent to connecting using ‘/’ with sqlplus.
References: #3705
[oracle] [bug] Fixed a bug in the result proxy used mainly by
Oracle when binary and other LOB types are in play, such that when query
/ statement caching were used, the type-level result processors, notably
that required by the binary type itself but also any other processor,
would become lost after the first run of the statement due to it being
removed from the cached result metadata.
References: #3699
misc
[bug] [examples] Changed the “directed graph” example to no longer
consider integer identifiers of nodes as significant; the “higher” /
“lower” references now allow mutual edges in both directions.
References: #3698
[bug] [py3k] Fixed bug in “to_list” conversion where a single bytes
object would be turned into a list of individual characters. This would
impact among other things using the Query.get() method on a primary key
that’s a bytes object.¶
References: #3660
On 05/16/2016 04:52 PM, Mike Bayer wrote:
SQLAlchemy release 1.0.13 is now available.
Release 1.0.13 fixes a variety of issues targeted at the 1.0 series that
have been resolved over the past several weeks. Fixes include small
issues repaired in the ORM, Core, Postgresql, Oracle, SQL Server
dialects. Most issues are very minor with the exception of one issue
involving Oracle LOB types in conjunction with query caching (such as
that used by the sqlalchemy.ext.baked) extension which would cause
result set fetches to fail.
Changelog for 1.0.13 is at:
http://www.sqlalchemy.org/changelog/CHANGES_1_0_13
SQLAlchemy 1.0.13 is available on the Download Page at:
http://www.sqlalchemy.org/download.html
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
