so process_revision_directives is a pathway here to the extent that
you need to modify the autogenerate process such that a table like
this is generated for you automatically.
However, Alembic's normal mode of usage is that the "autogenerate"
tool is only a time-saver, and is not intended to produ
>From issue here, closed as usage question:
https://bitbucket.org/zzzeek/alembic/issues/485/mssql-clustered-index-non-primary
Original question:
Is there a solution for autogenerating in a single pass MSSQL tables with a
primary key which isn't the clustered index, and a clustered index on a
d
