create_unique_constraint not working with naming conventions

Question

Migrated issue, originally created by Matt Jernigan ()

v0.8.4

autogenerate creates this:

op.create_unique_constraint('form_name', 'forms', ['org_code', 'form_name'])
op.drop_constraint('uq_forms_form_name', 'forms', type_='unique')

instead of this:

op.drop_constraint('uq_forms_form_name', 'forms', type_='unique')
op.create_unique_constraint(op.f('uq_forms_form_name'), 'forms', ['org_code', 'form_name'])

Several problems here:

1. Order: drop should be before create.
2. Create should maybe use op.f()
3. And, most notably, op.create_unique_constraint('form_name', ...) does not apply naming conventions (it creates a unique constraint called form_name in this case).

该提问来源于开源项目：sqlalchemy/alembic

Answer 1

Michael Bayer () wrote:

Hi there -

Unfortunately I have no idea what you are trying to do or how you are trying to do it. Alembic autogenerate does not detect changes in constraint names if that's what you're trying to do. Please provide minimal examples of the models in use both before and after the autogenerate operation.