0.5.0

Released: Thu Apr 4 2013Alembic 0.5.0 now requires at least
version 0.7.3 of SQLAlchemy to run properly.
Support for 0.6 has been dropped.

• [feature] Added version_table_schema argument
  to EnvironmentContext.configure(),
  complements the version_table argument to
  set an optional remote schema for the version
  table. Courtesy Christian Blume.

  References: #76

• [bug] [postgresql] Fixed format of RENAME for table that includes
  schema with Postgresql; the schema name shouldn't
  be in the "TO" field.

  References: #32

• [feature] Added output_encoding option to
  EnvironmentContext.configure(),
  used with --sql mode to apply an encoding
  to the output stream.

  References: #90

• [feature] Added Operations.create_primary_key()
  operation, will genenerate an ADD CONSTRAINT
  for a primary key.

  References: #93

• [bug] [mssql] Fixed bug whereby double quoting would be applied
  to target column name during an sp_rename
  operation.

  References: #109

• [bug] [mysql] [sqlite] transactional_ddl flag for SQLite, MySQL dialects
  set to False. MySQL doesn't support it,
  SQLite does but current pysqlite driver does not.

  References: #112

• [feature] upgrade and downgrade commands will list the
  first line of the docstring out next to the
  version number. Courtesy Hong Minhee.

  References: #115

• [feature] Added --head-only option to "alembic current",
  will print current version plus the symbol
  "(head)" if this version is the head or not.
  Courtesy Charles-Axel Dein.

• [bug] Autogenerate will render additional table keyword
  arguments like "mysql_engine" and others within
  op.create_table().

  References: #110

• [feature] The rendering of any construct during autogenerate
  can be customized, in particular to allow special rendering
  for user-defined column, constraint subclasses, using new
  render_item argument to
  EnvironmentContext.configure().

  References: #108

• [bug] Fixed bug whereby create_index()
  would include in the constraint columns that
  are added to all Table objects using events,
  externally to the generation of the constraint.
  This is the same issue that was fixed for unique
  constraints in version 0.3.2.

• [bug] Worked around a backwards-incompatible regression in Python3.3
  regarding argparse; running "alembic" with no arguments
  now yields an informative error in py3.3 as with all previous versions.
  Courtesy Andrey Antukh.

• [change] SQLAlchemy 0.6 is no longer supported by Alembic - minimum version is 0.7.3,
  full support is as of 0.7.9.

• [bug] A host of argument name changes within migration
  operations for consistency. Keyword arguments
  will continue to work on the old name for backwards compatibility,
  however required positional arguments will not:

  Operations.alter_column() - name -> new_column_name - old
  name will work for backwards compatibility.

  Operations.create_index() - tablename -> table_name -
  argument is positional.

  Operations.drop_index() - tablename -> table_name - old
  name will work for backwards compatibility.

  Operations.drop_constraint() - tablename -> table_name -
  argument is positional.

  Operations.drop_constraint() - type -> type_ - old
  name will work for backwards compatibility

  References: #104