0.6.3

Released: February 2, 2014

• [bug] Added a workaround for when we call fcntl.ioctl() to get at
  TERMWIDTH; if the function returns zero, as is reported to occur
  in some pseudo-ttys, the message wrapping system is disabled in the
  same way as if ioctl() failed.

  References: #172

• [feature] Added new argument
  EnvironmentContext.configure.user_module_prefix.
  This prefix is applied when autogenerate renders a user-defined type,
  which here is defined as any type that is from a module outside of the
  sqlalchemy. hierarchy. This prefix defaults to None, in
  which case the EnvironmentContext.configure.sqlalchemy_module_prefix
  is used, thus preserving the current behavior.

  References: #171

• [bug] Added support for autogenerate covering the use case where Table
  objects specified in the metadata have an explicit schema attribute
  whose name matches that of the connection's default schema
  (e.g. "public" for Postgresql). Previously, it was assumed that "schema"
  was None when it matched the "default" schema, now the comparison
  adjusts for this.

  References: #170

• [bug] The compare_metadata() public API function now takes into
  account the settings for
  EnvironmentContext.configure.include_object,
  EnvironmentContext.configure.include_symbol,
  and EnvironmentContext.configure.include_schemas, in the
  same way that the --autogenerate command does. Pull
  request courtesy Roman Podoliaka.

• [bug] Calling bulk_insert() with an empty list will not emit any
  commands on the current connection. This was already the case with
  --sql mode, so is now the case with "online" mode.

  References: #168

• [bug] Enabled schema support for index and unique constraint autodetection;
  previously these were non-functional and could in some cases lead to
  attribute errors. Pull request courtesy Dimitris Theodorou.

• [bug] More fixes to index autodetection; indexes created with expressions
  like DESC or functional indexes will no longer cause AttributeError
  exceptions when attempting to compare the columns.

  References: #164

• [feature] The ScriptDirectory system that loads migration files
  from a versions/ directory now supports so-called
  "sourceless" operation, where the .py files are not present
  and instead .pyc or .pyo files are directly present where
  the .py files should be. Note that while Python 3.3 has a
  new system of locating .pyc/.pyo files within a directory
  called __pycache__ (e.g. PEP-3147), PEP-3147 maintains
  support for the "source-less imports" use case, where the
  .pyc/.pyo are in present in the "old" location, e.g. next
  to the .py file; this is the usage that's supported even when
  running Python3.3.

  References: #163