0.8.10

0.8.10

Released: January 17, 2017

• [bug] [versioning] The alembic_version table, when initially created, now establishes a
  primary key constraint on the "version_num" column, to suit database
  engines that don't support tables without primary keys. This behavior
  can be controlled using the parameter
  EnvironmentContext.configure.version_table_pk. Note that
  this change only applies to the initial creation of the alembic_version
  table; it does not impact any existing alembic_version table already
  present.

  References: #406

• [batch] [bug] Fixed bug where doing batch_op.drop_constraint() against the
  primary key constraint would fail to remove the "primary_key" flag
  from the column, resulting in the constraint being recreated.

  References: #402

• [autogenerate] [bug] [oracle] Adjusted the logic originally added for #276 that detects MySQL
  unique constraints which are actually unique indexes to be generalized
  for any dialect that has this behavior, for SQLAlchemy version 1.0 and
  greater. This is to allow for upcoming SQLAlchemy support for unique
  constraint reflection for Oracle, which also has no dedicated concept of
  "unique constraint" and instead establishes a unique index.

• [bug] [versioning] Added a file ignore for Python files of the form .#<name>.py,
  which are generated by the Emacs editor. Pull request courtesy
  Markus Mattes.

  References: #356