0.6.5

0.6.5

Released: May 3, 2014

• [autogenerate] [bug] [mysql] This releases' "autogenerate index detection" bug, when a MySQL table
  includes an Index with the same name as a column, autogenerate reported
  it as an "add" even though its not; this is because we ignore reflected
  indexes of this nature due to MySQL creating them implicitly. Indexes
  that are named the same as a column are now ignored on
  MySQL if we see that the backend is reporting that it already exists;
  this indicates that we can still detect additions of these indexes
  but not drops, as we cannot distinguish a backend index same-named
  as the column as one that is user generated or mysql-generated.

  References: #202

• [environment] [feature] Added new feature EnvironmentContext.configure.transaction_per_migration,
  which when True causes the BEGIN/COMMIT pair to incur for each migration
  individually, rather than for the whole series of migrations. This is
  to assist with some database directives that need to be within individual
  transactions, without the need to disable transactional DDL entirely.

  References: #201

• [autogenerate] [bug] Fixed bug where the include_object() filter would not receive
  the original Column object when evaluating a database-only
  column to be dropped; the object would not include the parent
  Table nor other aspects of the column that are important
  for generating the "downgrade" case where the column is recreated.

  References: #200

• [bug] [environment] Fixed bug where EnvironmentContext.get_x_argument()
  would fail if the Config in use didn't actually
  originate from a command line call.

  References: #195

• [autogenerate] [bug] Fixed another bug regarding naming conventions, continuing
  from #183, where add_index()
  drop_index() directives would not correctly render the f()
  construct when the index contained a convention-driven name.

  References: #194