From 81e3d7bd00686b5e4d1e0b53db3eca9901c183c1 Mon Sep 17 00:00:00 2001 From: Sheogorath Date: Wed, 5 Sep 2018 15:08:32 +0100 Subject: Extend migration error handling The current error handling seems to conflict with some sequelize versions. So we add a second version of it in our excemptions. I'm not happy about it, but when it helps to prevent further migration breaking, it's worth it. Signed-off-by: Sheogorath --- lib/migrations/20161009040430-support-delete-note.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/migrations/20161009040430-support-delete-note.js') diff --git a/lib/migrations/20161009040430-support-delete-note.js b/lib/migrations/20161009040430-support-delete-note.js index 4df7a81c..39e6f7fb 100644 --- a/lib/migrations/20161009040430-support-delete-note.js +++ b/lib/migrations/20161009040430-support-delete-note.js @@ -2,7 +2,7 @@ module.exports = { up: function (queryInterface, Sequelize) { return queryInterface.addColumn('Notes', 'deletedAt', Sequelize.DATE).catch(function (error) { - if (error.message === "ER_DUP_FIELDNAME: Duplicate column name 'deletedAt'") { + if (error.message === "ER_DUP_FIELDNAME: Duplicate column name 'deletedAt'" || error.message === 'column "deletedAt" of relation "Notes" already exists') { console.log('Migration has already run… ignoring.') } else { throw error -- cgit v1.2.3