3
0

Fix column type on migration tables

This commit is contained in:
Denis Arh
2018-10-09 07:34:20 +02:00
parent 25dce4b7c3
commit 53940d6be9
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -2,7 +2,7 @@ CREATE TABLE IF NOT EXISTS `migrations` (
`project` varchar(16) NOT NULL COMMENT 'sam, crm, ...',
`filename` varchar(255) NOT NULL COMMENT 'yyyymmddHHMMSS.sql',
`statement_index` int(11) NOT NULL COMMENT 'Statement number from SQL file',
`status` varchar(16) NOT NULL COMMENT 'ok or full error message',
`status` TEXT NOT NULL COMMENT 'ok or full error message',
PRIMARY KEY (`project`,`filename`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+1 -1
View File
@@ -2,7 +2,7 @@ CREATE TABLE IF NOT EXISTS `migrations` (
`project` varchar(16) NOT NULL COMMENT 'sam, crm, ...',
`filename` varchar(255) NOT NULL COMMENT 'yyyymmddHHMMSS.sql',
`statement_index` int(11) NOT NULL COMMENT 'Statement number from SQL file',
`status` varchar(16) NOT NULL COMMENT 'ok or full error message',
`status` TEXT NOT NULL COMMENT 'ok or full error message',
PRIMARY KEY (`project`,`filename`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+1 -1
View File
@@ -2,7 +2,7 @@ CREATE TABLE IF NOT EXISTS `migrations` (
`project` varchar(16) NOT NULL COMMENT 'sam, crm, ...',
`filename` varchar(255) NOT NULL COMMENT 'yyyymmddHHMMSS.sql',
`statement_index` int(11) NOT NULL COMMENT 'Statement number from SQL file',
`status` varchar(16) NOT NULL COMMENT 'ok or full error message',
`status` TEXT NOT NULL COMMENT 'ok or full error message',
PRIMARY KEY (`project`,`filename`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;