From 51ef6a1dc30576f31a8a120066d81feedd0bf224 Mon Sep 17 00:00:00 2001 From: Ann Kamyshnikova Date: Wed, 4 Dec 2013 10:59:59 +0400 Subject: [PATCH] Fix mistake in usage drop_constraint parameters In migration e197124d4b9_add_unique_constrain mistake in usage drop_constraint parameter type_ and positional arguments name and table_name. The same mistake was already fixed in migration 63afba73813_ovs_tunnelendpoints_id_unique. Change-Id: I6a250e55ea53048bb11afd71fecf94da6f0c7421 Closes-bug: #1257607 --- .../versions/e197124d4b9_add_unique_constrain.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py b/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py index 897c8aac2..b2f4b5a87 100644 --- a/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py +++ b/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py @@ -59,7 +59,7 @@ def downgrade(active_plugins=None, options=None): return op.drop_constraint( - name=CONSTRAINT_NAME, - tablename=TABLE_NAME, - type='unique' + CONSTRAINT_NAME, + TABLE_NAME, + type_='unique' ) -- 2.45.2