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
This commit is contained in:
Ann Kamyshnikova 2013-12-04 10:59:59 +04:00
parent cc3ec4164d
commit 51ef6a1dc3
1 changed files with 3 additions and 3 deletions

View File

@ -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'
)