github sqlalchemy/alembic rel_0_7_1
0.7.1

latest releases: rel_1_15_2, rel_1_15_1, rel_1_15_0...
5 years ago

0.7.1

Released: December 3, 2014

  • [batch] [bug] The render_as_batch flag was inadvertently hardcoded to True,
    so all autogenerates were spitting out batch mode...this has been
    fixed so that batch mode again is only when selected in env.py.

  • [autogenerate] [feature] Support for autogenerate of FOREIGN KEY constraints has been added.
    These are delivered within the autogenerate process in the same
    manner as UNIQUE constraints, including include_object support.
    Big thanks to Ann Kamyshnikova for doing the heavy lifting here.

    References: #178

  • [batch] [feature] Added ~.Operations.batch_alter_table.naming_convention
    argument to Operations.batch_alter_table(), as this is necessary
    in order to drop foreign key constraints; these are often unnamed
    on the target database, and in the case that they are named, SQLAlchemy
    is as of the 0.9 series not including these names yet.

  • [batch] [bug] Fixed bug where the "source_schema" argument was not correctly passed
    when calling BatchOperations.create_foreign_key(). Pull
    request courtesy Malte Marquarding.

  • [batch] [bug] Repaired the inspection, copying and rendering of CHECK constraints
    and so-called "schema" types such as Boolean, Enum within the batch
    copy system; the CHECK constraint will not be "doubled" when the table is
    copied, and additionally the inspection of the CHECK constraint for
    its member columns will no longer fail with an attribute error.

    References: #249

  • [batch] [feature] Added two new arguments
    Operations.batch_alter_table.reflect_args
    and Operations.batch_alter_table.reflect_kwargs, so that
    arguments may be passed directly to suit the
    ~.sqlalchemy.schema.Table
    object that will be reflected.

Don't miss a new alembic release

NewReleases is sending notifications on new releases.