delta/python-packages/sqlalchemy-migrate.git, branch 0.9.3

Merge "pep8: mark all pep8 checks that currently fail as ignored"

2015-01-11T10:38:02+00:00

Merge "Use native sqlalchemy 0.9 quote attribute with ibmdb2"

2015-01-10T00:03:23+00:00

Ignore transaction management statements in SQL scripts

2015-01-09T22:32:27+00:00

Now that we don't run SQL script with a single .execute() call,
transaction management statements (BEGIN, COMMIT, END) fail with
operational error. Ignore them if occurred in a script.

All in all, transactions are managed by SQLAlchemy-migrate itself, so
there is no reason for the calling code to pass those statements in a
SQL script. Warn user about the statements that are ignored.

The ideal response to such a warning from library users is removing
those redundant transaction management statements from their scripts.

Note: ROLLBACK is not ignored even though it's one of transaction
management statements because its usage in migration scripts is insane
anyway, and we're better fail on it and not (almost) silently ignore it.

Change-Id: Ie4179c0e9341d42656d66821aaac23f8dcd33927
Closes-bug: 1368391

Use native sqlalchemy 0.9 quote attribute with ibmdb2

2015-01-09T22:31:28+00:00

Commit 8d6ce64cd08c0598963a92844495782997cd59f3 started using the native
quote attribute built into sqlalchemy 0.9 but missed the changes to the
ibmdb2 changeset, so alter table statements fail for DB2 on sqlalchemy
>= 0.9 (tested against 0.9.8).

This fixes the same issue for the ibmdb2 changeset.

Change-Id: Ia3fa6c3090b5eab29ed7746f4795d502990b8a2f

Don't add warnings filter on import

2015-01-08T22:22:59+00:00

The changeset module was adding a warnings filter on import. This
affects all applications that wind up importing it. A library
shouldn't modify the warnings filters unless asked.

Closes-Bug: #1407736
Change-Id: I893f8be48efd3d3642e977ab587c9e6dc867258b

Merge "Fix ibmdb2 unique constraint handling for sqlalchemy 0.9"

2014-10-10T12:32:25+00:00

pep8: mark all pep8 checks that currently fail as ignored

2014-08-23T19:34:13+00:00

Change-Id: Ic1dfb51598b920611acb1a0e437a32c5af90beda

SqlScript: execute multiple statements one by one

2014-08-23T19:34:13+00:00

Some drivers [f.e. MySQL Connector] do not like multiple statements
being passed to .execute(). They require either passing multi=True
parameter to .execute() that is not DB-API 2.0 defined, or executing
those statements one by one.

For that patch, I've chosen the second option to stay away from driver
specific hacks.

Also removed SQLite hack that seems to be related to the same multiple
statements issue.

blueprint enable-mysql-connector

Change-Id: Ic6d53ed1fef8aee9471f3540f06b39cd5ee4ef82

Make sure we don't throw away exception on SQL script failure

2014-08-23T19:34:13+00:00

If SQL script failed, we don't currently log the failure anywhere, so
users have hard time debugging an issue, if anything arises.

Let's log the failure before proceeding with rollback.

Change-Id: Ic92b1403c00bb238a68265a15150a4be6f6b2346

Pin testtools to < 0.9.36

2014-08-23T19:34:07+00:00

New testtools require that setUp() and tearDown() are not called twice,
while test_schema is built around multiple calls. So pinning the version
for now until a proper fix is implemented.

Closes-Bug: 1360252
Change-Id: I184db35242d036dacc7933c1d762cccc7f5c40bb