1.5.3

Released: January 29, 2021

bug

• [bug] [autogenerate] Changed the default ordering of "CREATE" and "DROP" statements indexes and
  unique constraints within the autogenerate process, so that for example in
  an upgrade() operation, a particular index or constraint that is to be
  replaced such as for a casing convention change will not produce any naming
  conflicts. For foreign key constraint objects, this is already how
  constraints are ordered, and for table objects, users would normally want
  to use Operations.rename_table() in any case.

  References: #786

• [bug] [autogenerate] [mssql] Fixed assorted autogenerate issues with SQL Server:

  -   ignore default reflected identity on primary_key columns
  
  -   improve server default comparison
  

  References: #787

• [bug] [autogenerate] [mysql] Fixed issue where autogenerate rendering of op.alter_column() would
  fail to include MySQL existing_nullable=False if the column were part
  of a primary key constraint within the table metadata.

  References: #788