Cinder SQL scripts assume too much about the environment and the way in
which they are executed by sqlalchemy-migrate. Particularly, they manage
transactions on their own even though sqlalchemy-migrate do it itself,
plus it assumes that scripts are executed in one go (even though
standard Python DB-API 2.0 does not mention multi-statement SQL commands
to be executed on DB cursors.
Reviewed: https:/ /review. openstack. org/121032 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=675e0e5889c ce269a758abf5fc 6933dd09b0f9fd
Committed: https:/
Submitter: Jenkins
Branch: master
commit 675e0e5889cce26 9a758abf5fc6933 dd09b0f9fd
Author: Ihar Hrachyshka <email address hidden>
Date: Fri Sep 12 10:57:34 2014 +0200
SQL scripts should not manage transactions
Cinder SQL scripts assume too much about the environment and the way in
which they are executed by sqlalchemy-migrate. Particularly, they manage
transactions on their own even though sqlalchemy-migrate do it itself,
plus it assumes that scripts are executed in one go (even though
standard Python DB-API 2.0 does not mention multi-statement SQL commands
to be executed on DB cursors.
blueprint enable- mysql-connector
Change-Id: I10c58b3af75d3a b9153a8bbd2a539 bf1577de328
Closes-Bug: 1368391