How to catch Sequelize Migration Errors and prevent adding migration to the SequelizeMeta table

Question

I've recently started to experiment with Sequelize Migrations using sequelize-cli. I noticed that if the migration script throws an error (using a try-catch block), sequelize-cli still updates the SequelizeMeta table with the migration as if it was successful.

What is the best way to catch errors and prevent Sequelize from entering the migration into the SequelizeMeta table on 'up', and conversely, prevent removing the migration when the 'down' script fails?

Why don't you like to throw exceptions? Seems like it's a natural approach of Sequelize CLI — Anatoly, Oct 13 '20 at 21:20
I did throw an exception, as I explained in my question, but sequelize-cli still updated the SequelizeMeta table as if the migration succeeded. — Tony Guinta, Oct 14 '20 at 04:53

Anatoly · Accepted Answer · 2020-10-14T06:44:36.240

Use a transaction to achieve rolling back all migration changes due to an exception like this:

    up: (queryInterface) => queryInterface.sequelize.transaction(
        async (transaction) => {
            await queryInterface.createTable(table, attributes, { transaction });
            if (some_condition) {
              throw new Error('Error while migrating');
            }
        }
),

Don't forget to indicate transaction in all Sequelize method calls.

Keep in mind that not all RDBMS support structure changes rolling back.

How to catch Sequelize Migration Errors and prevent adding migration to the SequelizeMeta table

1 Answers1