Glance 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.
Also fix comments to be actual SQL comments and not C comments
Reviewed: https:/ /review. openstack. org/121033 /git.openstack. org/cgit/ openstack/ glance/ commit/ ?id=92a7111e9e5 a9e3494ba1ce074 f673bc11328c63
Committed: https:/
Submitter: Jenkins
Branch: master
commit 92a7111e9e5a9e3 494ba1ce074f673 bc11328c63
Author: Ihar Hrachyshka <email address hidden>
Date: Fri Sep 12 11:02:31 2014 +0200
SQL scripts should not manage transactions
Glance 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.
Also fix comments to be actual SQL comments and not C comments
https:/ /blueprints. launchpad. net/oslo. db/+spec/ enable- mysql-connector
Change-Id: I10c58b3af75d3a b9153a8bbd2a539 bf1577de328
Closes-Bug: 1368391
Closes-Bug: 1410494