- b41f6c9 by jamesren · 14 years ago
- 53cd324 by jamesren · 14 years ago
- ef69298 Patch didn't work. Trying again by jamesren · 14 years ago
- 92afa56 Rebase the AUTOTEST_WEB database to schema version 51. Also default the by jamesren · 14 years ago
- fe6f1a4 Add option to database_connection so that logging can be turned on via object creation. by mbligh · 14 years ago
- 12454c6 Fix interactions with db_utils when simulating. Anyone attempting to by showard · 14 years ago
- 250d84d Merge the two databases and the two Django projects. Note that the TKO migrations are still present, as is the migration code for TKO in database/migrate.py. These pieces of code are preserved because they are required by this change to perform the merge. A separate change will be submitted in the future to remove those references. by showard · 14 years ago
- 12b4558 Massive permission fix by lmr · 14 years ago
- eab66ce Rename the tables in the databases, by prefixing the app name. This is by showard · 15 years ago
- b21b8c8 Fix handling of database reconnects in the scheduler by enhancing the "django" database_connection backend and having the scheduler use it. This eliminates the duplicate connection that the scheduler was setting up -- now it uses only a single connection (the Django one). by showard · 15 years ago
- 34ab099 beginnings of a new scheduler functional test. this aims to test the entire monitor_db.py file holistically, made possible by the fact that monitor_db.py is already isolated from all direct system access through drone_manager (this was a necessary separation for distributed scheduling). by mocking out the entire drone_manager, as well as other major dependencies (email manager, global config), and filling a test database, we can allow the dispatcher to execute normally and allow it to interact with all the other code in monitor_db. at the end, we can check the state of the database and the drone_manager, and (probably most importantly, given the usual failure mode of the scheduler) we can ensure no exceptions get raised from monitor_db. by showard · 15 years ago
- 6631273 Make a bunch of stuff executable by mbligh · 15 years ago
- 7c8ea99 Not all distros put a symlink in for the python version. However by mbligh · 15 years ago
- 049b0fd add a debug mode to migrations. this is pretty handy for debugging complex migrations. by showard · 15 years ago
- eca1f21 Make migration manager support migration modules with just strings "UP_SQL" and/or "DOWN_SQL". It seems to be a very common case that we just write SQL strings for up and down and then have some boilerplate migrate_up() and migrate_down() methods. Now we won't need those methods in that case. Of course, if you include those methods, they'll still get called instead. by showard · 15 years ago
- b82b1f2 Make a couple of errant files executable by mbligh · 15 years ago
- 89f84db by showard · 15 years ago
- 8bcd23a Move all MySQLdb imports after the 'import common' so that a MySQLdb by mbligh · 15 years ago
- a9a9101 Remove some dead code that was apparently left in database_connection.py. by showard · 16 years ago
- b1e5187 Get the scheduler unittest to run against SQLite! by showard · 16 years ago
- 0a4e022 Remove unused imports. by showard · 16 years ago
- 442e71e Move migration system into database/ directory. by showard · 16 years ago
- 0e73c85 Add a generic database wrapper, supporting different database backends, to be used by migrate, scheduler, parser (eventually), and maybe others. This will consolidate the multiple database wrappers we have throughout the code and allow us to swap in SQLite for MySQL for unit testing purposes. by showard · 16 years ago