d12da7c187
used custom column keys (e.g. using the ``key='foo'`` kwarg to ``Column``), the comparison of existing foreign keys to those specified in the metadata would fail, as the reflected table would not have these keys available which to match up. Foreign key comparison for autogenerate now ensures it's looking at the database-side names of the columns in all cases; this matches the same functionality within unique constraints and indexes. fixes #260
Running Unit Tests
Tests can be run be run using via py.test, via the nose front-end script, or the Python setup.py script:
py.test
python run_tests.py
python setup.py testThere's also a tox.ini file with several configurations:
toxSetting up Optional Databases
The test suite will attempt to run a subset of tests against various database backends, including Postgresql and MySQL. It uses the database URLs in the [db] section of setup.cfg to locate a URL for particular backend types. If the URL cannot be loaded, either because the requisite DBAPI is not present, or if the target database is found to be not accessible, the test is skipped.
To run tests for these backends, replace URLs with working ones inside the setup.cfg file. Setting a URL here requires that the corresponding DBAPI is installed as well as that the target database is running. A connection to the database should provide access to a blank schema, where tables will be created and dropped. It is critical that this schema have no tables in it already.
For Postgresql, it is also necessary that the target database contain a user-accessible schema called "test_schema".