0.8.4
0.8.4
Released: December 15, 2015
-
[feature] [versioning] A major improvement to the hash id generation function, which for some
reason used an awkward arithmetic formula against uuid4() that produced
values that tended to start with the digits 1-4. Replaced with a
simple substring approach which provides an even distribution. Pull
request courtesy Antti Haapala. -
[autogenerate] [feature] Added an autogenerate renderer for the
ExecuteSQLOp
operation
object; only renders if given a plain SQL string, otherwise raises
NotImplementedError. Can be of help with custom autogenerate
sequences that includes straight SQL execution. Pull request courtesy
Jacob Magnusson. -
[batch] [bug] Batch mode generates a FOREIGN KEY constraint that is self-referential
using the ultimate table name, rather than_alembic_batch_temp
.
When the table is renamed from_alembic_batch_temp
back to the
original name, the FK now points to the right name. This
will not work if referential integrity is being enforced (eg. SQLite
"PRAGMA FOREIGN_KEYS=ON") since the original table is dropped and
the new table then renamed to that name, however this is now consistent
with how foreign key constraints on other tables already operate
with batch mode; these don't support batch mode if referential integrity
is enabled in any case.References: #345
-
[autogenerate] [bug] Added a type-level comparator that distinguishes
Integer
,
BigInteger
, andSmallInteger
types and
dialect-specific types; these all have "Integer" affinity so previously
all compared as the same.References: #341
-
[batch] [bug] Fixed bug where the
server_default
parameter ofalter_column()
would not function correctly in batch mode.References: #338
-
[autogenerate] [bug] Adjusted the rendering for index expressions such that a
Column
object present in the sourceIndex
will not be rendered
as table-qualified; e.g. the column name will be rendered alone.
Table-qualified names here were failing on systems such as Postgresql.References: #337