Log Message:
py-alembic: updated to 1.4.0

1.4.0

[feature] [batch]

Added new parameters BatchOperations.add_column.insert_before, \ 
BatchOperations.add_column.insert_after which provide for establishing the \ 
specific position in which a new column should be placed. Also added \ 
Operations.batch_alter_table.partial_reordering which allows the complete set of \ 
columns to be reordered when the new table is created. Both operations apply \ 
only to when batch mode is recreating the whole table using \ 
recreate="always". Thanks to Marcin Szymanski for assistance with the \ 
implementation.

bug

[bug] [autogenerate]

Adjusted the unique constraint comparison logic in a similar manner as that of \ 
421 did for indexes in order to take into account SQLAlchemy’s own truncation \ 
of long constraint names when a naming convention is in use. Without this step, \ 
a name that is truncated by SQLAlchemy based on a unique constraint naming \ 
convention or hardcoded name will not compare properly.

[bug] [autogenerate]

A major rework of the “type comparison” logic is in place which changes the \ 
entire approach by which column datatypes are compared. Types are now compared \ 
based on the DDL string generated by the metadata type vs. the datatype \ 
reflected from the database. This means we compare types based on what would \ 
actually render and additionally if elements of the types change like string \ 
length, those changes are detected as well. False positives like those generated \ 
between SQLAlchemy Boolean and MySQL TINYINT should also be resolved. Thanks \ 
very much to Paul Becotte for lots of hard work and patience on this one.