0.6.6

Released: August 7, 2014

• [bug] A file named __init__.py in the versions/ directory is now
  ignored by Alembic when the collection of version files is retrieved.
  Pull request courtesy Michael Floering.

  References: #95

• [bug] Fixed Py3K bug where an attempt would be made to sort None against
  string values when autogenerate would detect tables across multiple
  schemas, including the default schema. Pull request courtesy
  paradoxxxzero.

• [bug] Autogenerate render will render the arguments within a Table construct
  using *[...] when the number of columns/elements is greater than
  255. Pull request courtesy Ryan P. Kelly.

• [bug] Fixed bug where foreign key constraints would fail to render in
  autogenerate when a schema name was present. Pull request courtesy
  Andreas Zeidler.

• [bug] Some deep-in-the-weeds fixes to try to get "server default" comparison
  working better across platforms and expressions, in particular on
  the Postgresql backend, mostly dealing with quoting/not quoting of various
  expressions at the appropriate time and on a per-backend basis.
  Repaired and tested support for such defaults as Postgresql interval
  and array defaults.

  References: #212

• [enhancement] When a run of Alembic command line fails due to CommandError,
  the output now prefixes the string with "FAILED:", and the error
  is also written to the log output using log.error().

  References: #209

• [bug] Liberalized even more the check for MySQL indexes that shouldn't be
  counted in autogenerate as "drops"; this time it's been reported
  that an implicitly created index might be named the same as a composite
  foreign key constraint, and not the actual columns, so we now skip those
  when detected as well.

  References: #208

• [feature] Added a new accessor MigrationContext.config, when used
  in conjunction with a EnvironmentContext and
  Config, this config will be returned. Patch
  courtesy Marc Abramowitz.