queryInterface.changeColumn(...) doesn't seem to work for changing ENUM set.

What are you doing?

I’m doing the following in my migration file:

  up: (queryInterface, Sequelize) => {
    queryInterface.changeColumn('data', 'sourceType', {
      type: Sequelize.ENUM(
        'FILE',
        'API',
      ),
      defaultValue: 'API'},
    )
  },

  down: (queryInterface, Sequelize) => {
    queryInterface.changeColumn('data', 'sourceType', {
      type: Sequelize.ENUM(
        'FILE',
        'API',
      ),
      defaultValue: 'API'},
    )
  }
};

What do you expect to happen?

Migrate the table and change existing sourceType column to be the new ENUM type.

What is actually happening?

I’m seeing the following error when running the migration:

Unhandled rejection SequelizeDatabaseError: type "enum_data_sourceType" already exists

Dialect: postgres Dialect version: (PostgreSQL) 10.0 Database version: XXX HUH? Sequelize version: Sequelize CLI [Node: 8.7.0, CLI: 3.0.0, ORM: 4.31.2] Tested with latest release: No (If yes, specify that version)

WARNING: This version of Sequelize CLI is not fully compatible with Sequelize v4. https://github.com/sequelize/cli#sequelize-support

3.0.0

… Just seeing this. Gonna post anyway to confirm (sorry) but does it sound like I need to update? Or is what I’m doing actually not supported?

[SvemirskiHod]

@ashok-sc thank you for the suggestion. I might end up doing the same.

Btw I’ve discovered that calling Sequelize.sync() once you have defined the new ENUM values in the model does the updates correctly. Not the best solution, but still a possibility.

It also seems that someone has written a package that handles the enum updates: https://www.npmjs.com/package/sequelize-replace-enum-postgres. I think I would rather migrate away from enums like you mentioned (and perhaps handle the value restrictions inside the model)

[sushantdhiman]

You are missing return in your migrations?