81e3d7bd00
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 <sheogorath@shivering-isles.com>
21 lines
779 B
JavaScript
21 lines
779 B
JavaScript
'use strict'
|
|
module.exports = {
|
|
up: function (queryInterface, Sequelize) {
|
|
return queryInterface.addColumn('Users', 'accessToken', Sequelize.STRING).then(function () {
|
|
return queryInterface.addColumn('Users', 'refreshToken', Sequelize.STRING)
|
|
}).catch(function (error) {
|
|
if (error.message === "ER_DUP_FIELDNAME: Duplicate column name 'accessToken'" || error.message === 'column "accessToken" of relation "Users" already exists') {
|
|
console.log('Migration has already run… ignoring.')
|
|
} else {
|
|
throw error
|
|
}
|
|
})
|
|
},
|
|
|
|
down: function (queryInterface, Sequelize) {
|
|
return queryInterface.removeColumn('Users', 'accessToken').then(function () {
|
|
return queryInterface.removeColumn('Users', 'refreshToken')
|
|
})
|
|
}
|
|
}
|