openstack
/
keystone
Code Issues Proposed changes

SQLAlchemy Change to support more strict dialect checking 

Update a couple DELETE operations within the test_sql_upgrade test
case to support the more strict dialect checking that occurs in
0.9.3 of SQLAlchemy for "additional arguments".

Closes-Bug: #1286717
Change-Id: I82b57257a8b49d798d813c65e76757021676ba90
This commit is contained in:
Morgan Fainberg 2014-03-01 21:31:54 -08:00
parent 42e23753f0
commit 622606d7b4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
keystone/tests/test_sql_upgrade.py
View File

@ -884,7 +884,7 @@ class SqlUpgradeTests(SqlMigrateBase):
# two uses with clashing name as we try to revert to a single global
# name space. This limitation is raised as Bug #1125046 and the delete
# could be removed depending on how that bug is resolved.
cmd = this_table.delete(id=user['id'])
cmd = this_table.delete().where(this_table.c.id == user['id'])
self.engine.execute(cmd)
# Now, the Project table.
@ -908,7 +908,7 @@ class SqlUpgradeTests(SqlMigrateBase):
# TODO(henry-nash): For now, we delete one of the projects for the same
# reason as we delete one of the users (Bug #1125046). This delete
# could be removed depending on that bug resolution.
cmd = this_table.delete(id=project['id'])
cmd = this_table.delete().where(this_table.c.id == project['id'])
self.engine.execute(cmd)
def test_upgrade_trusts(self):