aboutsummaryrefslogtreecommitdiffstats
path: root/mediagoblin/tests/test_sql_migrations.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove remaining imports/calls to six not automatically removed by pyupgrade.Ben Sturmfels2021-03-051-2/+0
|
* Apply `pyupgrade --py3-plus` to remove Python 2 compatibility code.Ben Sturmfels2021-03-051-133/+133
|
* Fix dependencies and tests for clean Python 2 & 3 test runs under Docker.Ben Sturmfels2020-04-281-0/+1
| | | | | This change gives a clean test run in the Debian-based Python 2 and Python 3 docker images.
* tests: Fix migration tests; foundations are now installed separatelyChristopher Allan Webber2016-03-291-29/+9
| | | | | | | * mediagoblin/tests/test_sql_migrations.py: Import migration.changeset even in python 3. (FOUNDATIONS): Removed. (test_set1_to_set3): Removed foundations checks.
* tests: importorskip migration tests on "migrate" rather than on Python 3Christopher Allan Webber2016-03-291-1/+1
| | | | | | | | | Previously we assumed we wouldn't run migration tests if we're on Python 3, but now that we support sqlalchemy-migrate with Python 3, switch to checking based on "migrate" importability. * mediagoblin/tests/test_sql_migrations.py: Update test skipping to rely on "migrate" module presence rather than Python 3 check.
* Skip test_sql_migrations on Python 3 for now.Berker Peksag2014-07-281-3/+7
|
* Use six.iteritems() instead of dict.iteritems().Berker Peksag2014-05-261-1/+3
|
* I added a few more unitests in this commit. It now confirms that even after mi-tilly-Q2013-07-311-1/+11
| | | | -gration, there is only one of each Foundation object.
* In this commit I added a few unittests to account for Foundations. There weretilly-Q2013-07-311-6/+21
| | | | | only a few tests I had to add to mediagoblin/tests/test_sql_migrations.py beca- -use the foundation creation only happens at database initialization.
* Starting to write unit tests...tilly-Q2013-07-301-5/+8
|
* Reverting "Always activate testing in every test module ever."Christopher Allan Webber2013-05-171-3/+0
| | | | | | Revert "Always activate testing in every test module ever." This reverts commit 0536306048daa0970d2e43411ba2a9bf073e570e.
* Always activate testing in every test module ever.Christopher Allan Webber2013-05-161-0/+3
| | | | Kind of a dorky way to implement this, but...
* Move db.sql.migration_tools to db.migration_tools.Elrond2013-01-081-1/+1
| | | | Follow the new trend.
* Move all the migration tools into new migration_tools.pyElrond2013-01-081-1/+1
| | | | | | | | | Factor all the migration related stuff out into a new .db.sql.migration_tools. First we don't have to load this module for our normal server. Second it makes all the import dependencies a little more cleaner.
* Mv db.sql.base to db.baseSebastian Spaeth2013-01-071-1/+1
| | | | | | | | This concludes the db.sql.* -> db.* move. Our db abstraction layer is sqlalchemy, so there is no need to a separate db.sql.* hierarchy. All tests have been run for each of the commit series to make sure everything works at every step.
* Move db.sql.util to db.utilSebastian Spaeth2013-01-071-1/+1
| | | | | | | | Now that sqlalchemy is providing the database abstractions, there is no need to hide everything in db.sql. sub-modules. It complicates the code and provides a futher layer of indirection. Move the db.sql.util.py to db.util.py and adapt the importers.
* Add a UniqueConstraint add test in test_sql_migrationsChristopher Allan Webber2012-12-051-3/+26
| | | | | We should have this anyway, and Elrond needs it to help fix current broken migration thingies.
* Moving the "dependency injection printer tools" over to tools/common.pyChristopher Allan Webber2012-07-141-12/+1
|
* Level exits are Unicode too.Brett Smith2012-07-041-3/+3
|
* Make sure MigrationManagers always get Unicode names.Brett Smith2012-07-041-4/+4
| | | | | If we fail to do this, SQLAlchemy complains that we're binding a non-Unicode value to a Unicode column.
* Commenting out the migrations that don't exist yetChristopher Allan Webber2012-02-181-4/+4
|
* Explained why migration #1 commented out.Christopher Allan Webber2012-01-291-0/+3
|
* Excepting that migration 1 doesn't work(!), sqlalchemy migration branch workingChristopher Allan Webber2012-01-291-36/+72
| | | | | | | The reason migration 1 doesn't work, and is commented out, is because of sqlalchemy-migrate not handling certain constraints while dropping binary sqlite columns right. See also: http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=143&thanks=143&ts=1327882242
* db_conn.engine -> db_conn.bindChristopher Allan Webber2012-01-291-21/+21
|
* Migration manager's current migration should be 3, not 7, after running all ↵Christopher Allan Webber2012-01-291-3/+3
| | | | migrations!
* Fixed the descriptions for the necroplex!Christopher Allan Webber2012-01-291-2/+2
|
* assert column type from Unicode -> VARCHAR. SQLAlchemy reflection only so ↵Christopher Allan Webber2012-01-291-29/+29
| | | | smart ;)
* printer = CollectingPrinter -> printer = CollectingPrinter()Christopher Allan Webber2012-01-291-2/+2
|
* CollectingPrinter is a class, not a function!Christopher Allan Webber2012-01-291-1/+1
|
* magical_powers relationship set on wrong table, fixedChristopher Allan Webber2012-01-291-1/+1
|
* Migration records are dicts, not lists. Fix SET1_MIGATIONS!Christopher Allan Webber2012-01-291-1/+1
|
* test_set1_to_set3() now has appropriate amount of code, even if it doesn't ↵Christopher Allan Webber2012-01-291-8/+37
| | | | run :)
* Fixing some obvious errors caught by pyflakesChristopher Allan Webber2012-01-291-21/+25
|
* More stuff even yet per sql migration stuff! And still not ready!Christopher Allan Webber2012-01-291-4/+4
|
* Closer to the end of this migration test...Christopher Allan Webber2012-01-291-2/+70
|
* unicode stuff and more bits on the actual migration methodChristopher Allan Webber2012-01-291-89/+214
|
* A ton more work on the SQL migration unit tests...Christopher Allan Webber2012-01-291-5/+85
|
* Wrote up some scaffolding for the actual testsChristopher Allan Webber2012-01-291-3/+53
|
* Insert migration objects round 3Christopher Allan Webber2012-01-291-0/+87
|
* Wrote some (semi-silly) descriptions of each migrationChristopher Allan Webber2012-01-291-0/+18
|
* Docstrings for stage 2 migrationsChristopher Allan Webber2012-01-291-0/+19
|
* Theoretical full set of migration2 objects to insert for testingChristopher Allan Webber2012-01-291-1/+76
|
* Insert migration1 objects. Also, Level1 id from Integer->UnicodeChristopher Allan Webber2012-01-291-7/+43
|
* All theoretical migrations written!Christopher Allan Webber2012-01-291-5/+25
|
* binding migration metadata to engine, and level_exits_new_table should now workChristopher Allan Webber2012-01-291-6/+6
|
* More test migration work. Closing to working migrations for set 2...Christopher Allan Webber2012-01-291-5/+62
| | | | Also, this file is written in 2012, correct that ;)
* Might as well call it "set2 migrations"Christopher Allan Webber2012-01-291-1/+1
|
* A theoretical set of models to migrate about with, plus one migration ;)Christopher Allan Webber2012-01-291-0/+177
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-07 20:24:14 +0000