1320914 - Differences in the classified_failure tables between environments

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

Only minor, but might as well sync up:

--- vagrant.sql	2016-11-25 17:22:53.439965200 +0000
+++ prod.sql	2016-11-25 17:31:49.775087600 +0000
...
 --
 -- Table structure for table `classified_failure`
 --
 
 DROP TABLE IF EXISTS `classified_failure`;
 /*!40101 SET @saved_cs_client     = @@character_set_client */;
 /*!40101 SET character_set_client = utf8 */;
 CREATE TABLE `classified_failure` (
   `id` bigint(20) NOT NULL AUTO_INCREMENT,
   `bug_number` int(10) unsigned DEFAULT NULL,
-  `created` datetime(6) NOT NULL,
-  `modified` datetime(6) NOT NULL,
+  `created` datetime NOT NULL,
+  `modified` datetime NOT NULL,
   PRIMARY KEY (`id`),
   UNIQUE KEY `<INDEX_NAME>` (`bug_number`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
 /*!40101 SET character_set_client = @saved_cs_client */;

Comment 1

[Ed Morley [:emorley]]

Similar to bug 1320913 comment 3, I've fixed the datetime differences on dev/stage/prod using:

ALTER TABLE `treeherder`.`classified_failure` MODIFY `created` DATETIME(6) NOT NULL;
ALTER TABLE `treeherder`.`classified_failure` MODIFY `modified` DATETIME(6) NOT NULL;