Closed
Bug 1335464
Opened 7 years ago
Closed 7 years ago
Differences in the bug_job_map table schema between environments
Categories
(Tree Management :: Treeherder, defect, P2)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Diff of vagrant->prod: CREATE TABLE `bug_job_map` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `bug_id` int(10) unsigned NOT NULL, `created` datetime(6) NOT NULL, `job_id` bigint(20) NOT NULL, - `user_id` int(11), + `user_id` int(11) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `<NAME>` (`job_id`,`bug_id`), KEY `<NAME>` (`bug_id`), KEY `<NAME>` (`user_id`), CONSTRAINT `<NAME>` FOREIGN KEY (`job_id`) REFERENCES `job` (`id`), CONSTRAINT `<NAME>` FOREIGN KEY (`user_id`) REFERENCES `auth_user` (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
Assignee | ||
Comment 1•7 years ago
|
||
The difference is a no-op really, since an unspecified default for this field type is the same as a DEFAULT NULL, but for the sake of easing schema comparisons, I've run this against dev/stage/prod: ALTER TABLE `treeherder`.`bug_job_map` ALTER COLUMN `user_id` DROP DEFAULT;
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•