sqlalchemy-migrate/migrate/tests/fixture
Roman Podolyaka a91766a1ac Run tests on PostgreSQL and MySQL too
In addition to running tests with different Python and SQLAlchemy
versions, they should also be run on different DB backends, which
are used in production (PostgreSQL and MySQL).

This patch:
  - modifies test_db.cfg to run tests on PostgreSQL and MySQL
    (Jenkins Slave credentials are used here, to ensure these
    tests are always run by Jenkins gate); if a backend is not
    available, test cases will be skipped for it
  - concurrency is set to 1 (sharing of the one MySQL or PostgreSQL
    DB among different test runner processes would lead to
    race conditions)
  - fixes tests dropping FK columns in MySQL: in earlier MySQL
    versions dropping a column that is a part of a FK constraint
    would lead to dropping of the FK too. As of MySQL 5.5 that's
    not the case anymore: if one tries to drop such column, he/she
    will get a very obscure error (something like "Error on rename
    of './openstack_citest/#sql-4af_aa2' to './openstack_citest/tmp_adddropcol'
    (errno: 150)") '\nALTER TABLE tmp_adddropcol DROP COLUMN r2').
    So the solution if to drop FK constraints first, and only then
    the columns it is made up of

Change-Id: I8c5d2874c83e7df46da69969ed54d85437c849e7
2013-10-12 07:04:33 +00:00
..
__init__.py Updated to OpenStack Build stuff. 2013-07-11 16:54:46 -04:00
base.py Updated to OpenStack Build stuff. 2013-07-11 16:54:46 -04:00
database.py Run tests on PostgreSQL and MySQL too 2013-10-12 07:04:33 +00:00
models.py move tests/ directory into migrate/tests (much better form) and fix all import lines and other minor issues 2010-06-10 18:08:06 +01:00
pathed.py move tests/ directory into migrate/tests (much better form) and fix all import lines and other minor issues 2010-06-10 18:08:06 +01:00
shell.py fix SA06 compatibility in tests 2010-07-07 19:27:26 +02:00
warnings.py use _index_identifier instead of _validate_identifier if 2010-11-09 21:38:17 +01:00