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.

0.9.9

0.9.9

Released: March 22, 2018

• [commands] [feature] Added new flag --indicate-current to the alembic history command.
  When listing versions, it will include the token "(current)" to indicate
  the given version is a current head in the target database. Pull request
  courtesy Kazutaka Mise.

  References: #481

• [autogenerate] [bug] [mysql] The fix for #455 in version 0.9.6 involving MySQL server default
  comparison was entirely non functional, as the test itself was also broken
  and didn't reveal that it wasn't working. The regular expression to compare
  server default values like CURRENT_TIMESTAMP to current_timestamp() is
  repaired.

  References: #455

• [autogenerate] [bug] [mysql] Fixed bug where MySQL server default comparisons were basically not working
  at all due to incorrect regexp added in #455. Also accommodates
  for MariaDB 10.2 quoting differences in reporting integer based server
  defaults.

  References: #483

• [bug] [mysql] [operations] Fixed bug in op.drop_constraint() for MySQL where
  quoting rules would not be applied to the constraint name.

  References: #487

0.9.8

0.9.8

Released: February 16, 2018

• [bug] [runtime] Fixed bug where the Script.as_revision_number() method
  did not accommodate for the 'heads' identifier, which in turn
  caused the EnvironmentContext.get_head_revisions()
  and EnvironmentContext.get_revision_argument() methods
  to be not usable when multiple heads were present.
  The :meth:.EnvironmentContext.get_head_revisions method returns
  a tuple in all cases as documented.

  References: #482

• [autogenerate] [bug] [postgresql] Fixed bug where autogenerate of ExcludeConstraint
  would render a raw quoted name for a Column that has case-sensitive
  characters, which when invoked as an inline member of the Table
  would produce a stack trace that the quoted name is not found.
  An incoming Column object is now rendered as sa.column('name').

  References: #478

• [autogenerate] [bug] Fixed bug where the indexes would not be included in a
  migration that was dropping the owning table. The fix
  now will also emit DROP INDEX for the indexes ahead of time,
  but more importantly will include CREATE INDEX in the
  downgrade migration.

  References: #468

• [bug] [postgresql] Fixed the autogenerate of the module prefix
  when rendering the text_type parameter of
  postgresql.HSTORE, in much the same way that
  we do for ARRAY's type and JSON's text_type.

  References: #480

• [bug] [mysql] Added support for DROP CONSTRAINT to the MySQL Alembic
  dialect to support MariaDB 10.2 which now has real
  CHECK constraints. Note this change does not
  add autogenerate support, only support for op.drop_constraint()
  to work.

  References: #479