1304088 - Differences in the result_set schemas between environments

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

For the per-repo `result_set` table, Vagrant has a `NOT NULL` condition on the `last_modified` field, ie:

  `last_modified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

...whereas some environments have:

  `last_modified` timestamp NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

(And in some cases, it's a mixture between project DBs, since newly added projects will have picked up the changes to the in-repo SQL.)

This is presumably leftover from having to add `last_modified` with a default value initially, in bug 1196804.

Cleaning this up will likely just be a case of running the appropriate `./manage.py run_sql ...` command to alter the field across all projects. (If it were anything more complex, it probably wouldn't be worth it, given per-project repos going away.)

Comment 1

[Ed Morley [:emorley]]

Wontfix since we're going to be dropping these tables once the datasource->ORM migration (bug 1178641) is complete.