1.0.8

1.0.8

Released: March 4, 2019

• [bug] [operations] Removed use of deprecated force parameter for SQLAlchemy quoting
  functions as this parameter will be removed in a future release.
  Pull request courtesy Parth Shandilya(ParthS007).

  References: #528

• [autogenerate] [bug] [postgresql] [py3k] Fixed issue where server default comparison on the PostgreSQL dialect would
  fail for a blank string on Python 3.7 only, due to a change in regular
  expression behavior in Python 3.7.

  References: #541

1.0.7

1.0.7

Released: January 25, 2019

• [autogenerate] [bug] Fixed issue in new comment support where autogenerated Python code
  for comments wasn't using repr() thus causing issues with
  quoting. Pull request courtesy Damien Garaud.

  References: #529

1.0.6

1.0.6

Released: January 13, 2019

• [feature] [operations] Added Table and Column level comments for supported backends.
  New methods Operations.create_table_comment() and
  Operations.drop_table_comment() are added. A new arguments
  Operations.alter_column.comment and
  Operations.alter_column.existing_comment are added to
  Operations.alter_column(). Autogenerate support is also added
  to ensure comment add/drops from tables and columns are generated as well
  as that Operations.create_table(), Operations.add_column()
  both include the comment field from the source Table
  or Column object.

  References: #422

1.0.5

1.0.5

Released: November 27, 2018

• [bug] [py3k] Resolved remaining Python 3 deprecation warnings, covering
  the use of inspect.formatargspec() with a vendored version
  copied from the Python standard library, importing
  collections.abc above Python 3.3 when testing against abstract
  base classes, fixed one occurrence of log.warn(), as well as a few
  invalid escape sequences.

  References: #507

1.0.4

1.0.4

Released: November 27, 2018

• [change] Code hosting has been moved to GitHub, at
  https://github.com/sqlalchemy/alembic. Additionally, the
  main Alembic website documentation URL is now
  https://alembic.sqlalchemy.org.

1.0.3

1.0.3

Released: November 14, 2018

• [bug] [mssql] Fixed regression caused by #513, where the logic to consume
  mssql_include was not correctly interpreting the case where the flag
  was not present, breaking the op.create_index directive for SQL Server
  as a whole.

  References: #516

1.0.2

1.0.2

Released: October 31, 2018

• [autogenerate] [bug] The system=True flag on Column, used primarily in conjunction
  with the Postgresql "xmin" column, now renders within the autogenerate
  render process, allowing the column to be excluded from DDL. Additionally,
  adding a system=True column to a model will produce no autogenerate diff as
  this column is implicitly present in the database.

  References: #515

• [bug] [mssql] Fixed issue where usage of the SQL Server mssql_include option within a
  Operations.create_index() would raise a KeyError, as the additional
  column(s) need to be added to the table object used by the construct
  internally.

  References: #513

1.0.1

1.0.1

Released: October 17, 2018

• [bug] [commands] Fixed an issue where revision descriptions were essentially
  being formatted twice. Any revision description that contained
  characters like %, writing output to stdout will fail because
  the call to config.print_stdout attempted to format any
  additional args passed to the function.
  This fix now only applies string formatting if any args are provided
  along with the output text.

  References: #497

• [autogenerate] [bug] Fixed issue where removed method union_update() was used when a
  customized MigrationScript instance included entries in the
  .imports data member, raising an AttributeError.

  References: #512

1.0.0

1.0.0

Released: July 13, 2018

• [feature] [general] For Alembic 1.0, Python 2.6 / 3.3 support is being dropped, allowing a
  fixed setup.py to be built as well as universal wheels. Pull request
  courtesy Hugo.

  References: #491

• [feature] [general] With the 1.0 release, Alembic's minimum SQLAlchemy support version
  moves to 0.9.0, previously 0.7.9.

• [batch] [bug] Fixed issue in batch where dropping a primary key column, then adding it
  back under the same name but without the primary_key flag, would not remove
  it from the existing PrimaryKeyConstraint. If a new PrimaryKeyConstraint
  is added, it is used as-is, as was the case before.

  References: #502

0.9.10

0.9.10

Released: June 29, 2018

• [autogenerate] [bug] The "op.drop_constraint()" directive will now render using repr() for
  the schema name, in the same way that "schema" renders for all the other op
  directives. Pull request courtesy Denis Kataev.

• [autogenerate] [bug] Added basic capabilities for external dialects to support rendering of
  "nested" types, like arrays, in a manner similar to that of the Postgresql
  dialect.

  References: #494

• [autogenerate] [bug] Fixed issue where "autoincrement=True" would not render for a column that
  specified it, since as of SQLAlchemy 1.1 this is no longer the default
  value for "autoincrement". Note the behavior only takes effect against the
  SQLAlchemy 1.1.0 and higher; for pre-1.1 SQLAlchemy, "autoincrement=True"
  does not render as was the case before. Pull request courtesy Elad Almos.