:version: 0.6.1
:released: no release date
+ .. change::
+ :tags: feature
+ :tickets: 107
+
+ Support for autogeneration detection and rendering of indexes and
+ unique constraints has been added. The logic goes through some effort
+ in order to differentiate between true unique constraints and
+ unique indexes, where there are some quirks on backends like Postgresql.
+ The effort here in producing the feature and tests is courtesy of IJL.
+
.. change::
:tags: bug
* Table additions, removals.
* Column additions, removals.
* Change of nullable status on columns.
+* Basic changes in indexes and unique constraints
+
+.. versionadded:: 0.6.1 Support for autogenerate of indexes and unique constraints.
Autogenerate can *optionally* detect:
Autogenerate can't currently, but will *eventually* detect:
-* Free-standing constraint additions, removals,
- like CHECK, UNIQUE, FOREIGN KEY - these aren't yet implemented.
- Right now you'll get constraints within new tables, PK and FK
- constraints for the "downgrade" to a previously existing table,
- and the CHECK constraints generated with a SQLAlchemy "schema" types
- :class:`~sqlalchemy.types.Boolean`, :class:`~sqlalchemy.types.Enum`.
-* Index additions, removals - not yet implemented.
+* Some free-standing constraint additions and removals,
+ like CHECK and FOREIGN KEY - these are not fully implemented.
* Sequence additions, removals - not yet implemented.
Rendering Custom Types in Autogenerate