News and Updates
SQLAlchemy 1.0.12 Released
SQLAlchemy release 1.0.12 is now available.
Release 1.0.12 is a bug fix release resolving a handful of issues reported in the past few weeks. Primary development continues on the 1.1 series which is slated for initial releases in the spring.
1.0.12 includes relatively minor fixes, including a revision to a fix made for version 1.0.10 where we're attempting to report on the "cause" of an error that is interrupted by a later failure to emit a ROLLBACK on the MySQL platform. While Python 3 solves this problem using exception chaining and cause reporting, on Python 2 we emit a warning so that the cause isn't totally concealed. The condition has been expanded to emit this warning in a much wider range of scenarios.
Changelog for 1.0.12 is at:
SQLAlchemy 1.0.12 is available on the Download Page.
SQLAlchemy 1.0.11 Released
SQLAlchemy release 1.0.11 is now available.
Release 1.0.11, only twelve days after 1.0.10's release, is expedited to correct for one ORM-related regression introduced by a 1.0.10 fix; some other fairly significant bugfixes involving more recently added features, all reported subsequent to the release of 1.0.10, were also fixed. Fixes include a major issue in the "baked lazy loader" extension when used as a systemwide-replacement for lazy loading, a major series of fixes to the "eager_defaults" mapper persistence option, and a revision to 1.0.10's fix for a particular polymorphic joined-eager loading issue.
Changelog for 1.0.11 is at:
SQLAlchemy 1.0.11 is available on the Download Page.
SQLAlchemy 1.0.10 Released
SQLAlchemy release 1.0.10 is now available.
Release 1.0.10 continues with maintenance fixes as we continue major development on the 1.1 series. Fixes here include a handful of fairly obscure ORM issues, as our userbase continues to use the new loader option system introduced in 0.9 more deeply, some adjustments to internals to work more smoothly with the latest Python 3.5 and upcoming 3.6 versions, an array of dialect-specific fixes, and a pretty important fix to the new "baked query" extension. There's also one new feature which is the ability to render an UPDATE statement with a specific ordering of the SET clauses.
Changelog for 1.0.10 is at:
SQLAlchemy 1.0.10 is available on the Download Page.
SQLAlchemy 1.0.9 Released
SQLAlchemy release 1.0.9 is now available.
Release 1.0.9 is a bugfix release, pushing out a collection of mostly small fixes that have accumulated over the past few months. In particular there is one small but important fix for users of the latest cx_Oracle library (5.2 or greater) in conjunction with Python 3 that corrects for an important issue in correctly detecting the version of this DBAPI and its Unicode behavior.
Primary development of new features, architectural and behavioral improvements continues within the 1.1 series targeted at early 2016 for initial beta releases.
Changelog for 1.0.9 is at:
SQLAlchemy 1.0.9 is available on the Download Page.
Alembic 0.8.0 Relased
Alembic 0.8.0 is now available.
This release includes a large series of reorganizations in order to provide several new extension APIs which dramatically increase the degree to which Alembic can be extended.
The average Alembic environment should hopefully not notice anything different as we've strived to maintain full backwards compatibility. However, both the "operations" and the "autogenerate" features have been entirely reorganized in order to produce a much more open-ended and integrated flow between these two systems.
At the base of the new system, everything in Alembic that is an "operation" is now boiled down into an object, known as a MigrateOperation. Subclasses of MigrateOperation include familiar things like AddColumnOp, CreateForeignKeyOP, and DropTableOp. These objects don't represent the SQL that we emit for these operations, but instead, represent the operation as defined in Alembic as part of the interface. On these objects we now hang all functions as related operations, including how it is linked to the alembic.op.* namespace, how autogenerate renders it in Python, how autogenerate produces a "diff" of it against a database, how it is implemented against the DDL backend, and many more things.
With this new system, we haven't necessarily added any new functionality that wasn't there before, but we've now organized all the things we know about an "Alembic operation" centered around this object using now-public APIs to associate operations with each one.
What this means is that you can now:
- create your own Alembic operations freely, which become available as first-class functions in alembic.op.* like any other
- create your own autogenerate schemes for these operations, including defining how to do the database compare as well as render the Python
- Modify completely what autogenerate does when it produces a new migration script; the entire contents of a generated script are delivered in object form to user-available hooks which can then rewrite the structure completely. The autogenerate operation can be made to generate multiple files to different directories and/or branches, or no files at all. A helper is also provided to make it easy to write short replacements of specific elements. Common user requests such as having autogenerate not produce a file if there were no net changes, converting an "add column" operation into an "add column, nullable=True" + "alter column set not null", or supporting alternative migration flows such as splitting migrations into "expand" and "contract" branches are now easily scriptable with no need to add new flags and switches to Alembic itself.
- Create applications that can receive an autogenerate stream and push it out directly as Alembic operations to a live database or SQL script, without even generating any revision scripts.
- Create alternative series of implementations for Alembic operations, such as writing them out to JSON or XML formats or perhaps building up a live MetaData structure based on them.
The release also includes a few other fixes and features. In particular, in conjunction with the reorganization of operations, there is also a renaming of positional arguments in the alembic.op.* namespace, however a backwards-compatibility translation layer is included so that most projects should be unaffected. The full list of name changes is listed in the changelog.
Download Alembic 0.8.0 at: https://pypi.python.org/pypi/alembic/
Full changelog, including new features, bugfixes, as well as links to all Operations methods where positional argument names that have changed, are at: http://alembic.readthedocs.org/en/latest/changelog.html#change-0.8.0.
Thanks to everyone in the community who has helped with this release in the form of patches, pull requests, bug reports, and mailing list commentary.