0.9.2
Released: May 18, 2017
-
[bug] [mssql] Repaired
Operations.rename_table()
for SQL Server when the
target table is in a remote schema, the schema name is omitted from
the "new name" argument.References: #429
-
[commands] [feature] Added a new configuration option
timezone
, a string timezone name
that will be applied to the create date timestamp rendered
inside the revision file as made availble to thefile_template
used
to generate the revision filename. Note this change adds the
python-dateutil
package as a dependency.References: #425
-
[autogenerate] [bug] The autogenerate compare scheme now takes into account the name truncation
rules applied by SQLAlchemy's DDL compiler to the names of the
Index
object, when these names are dynamically truncated
due to a too-long identifier name. As the identifier truncation is
deterministic, applying the same rule to the metadata name allows
correct comparison to the database-derived name.References: #421
-
[bug environment] A warning is emitted when an object that's not a
~sqlalchemy.engine.Connection
is passed to
EnvironmentContext.configure()
. For the case of a
~sqlalchemy.engine.Engine
passed, the check for "in transaction"
introduced in version 0.9.0 has been relaxed to work in the case of an
attribute error, as some users appear to be passing an
~sqlalchemy.engine.Engine
and not a
~sqlalchemy.engine.Connection
.References: #419