I try to add new column and foreign key

migration.addColumn('user', 'level_id', {
  type: DataTypes.INTEGER.UNSIGNED,
  references: 'level',
  referenceKey: 'id',
  onUpdate: 'cascade',
  onDelete: 'restrict'
});

The column will be successfully created but without foreign key.
Does it support now?
Thanks

@theoptz No, this issues is not resolved yet. The current code only handles foreign keys in the context of table creation, not column updates.

👍

👀 Waiting for this issue

👍

👍 Would be great to be able to remove foreign keys as well. I am converting a 1:many relationship to a many:many and need to remove the original foreign key constraint.

👍

Also fail on migration.renameColumn if it has a constraint.

Not related to original issue but addColumn should now support foreign key constraints as of 0c1ec1c

I'm using v2.0-rc1, and addColumn still doesn't create the foreign key - is this supposed to functional in this release?

This is the migration code:

migration.addColumn('Paintings', 'ArtistId', {
  type: DataTypes.INTEGER,
  references: 'Artists',
  referencesKey: 'id',
  onUpdate: 'CASCADE',
  onDelete: 'RESTRICT'
});

The issue is still open, so yes, it's still an issue :)

:) That was in reference to the comment above : Not related to original issue but addColumn should now support foreign key constraints as of 0c1ec1c.

Original issue was about changeColumn , comment seemed to suggest using addColumn instead would work now.

Well the unit test added in that commit passes, so addColumn is partially implemented atleast.
Please provide a pull request with a failing unit test and i'll get a fix in for you.

Waiting too
👍

Me too.

+1

+1 +1

I'm using sequelize "^2.0.0-rc2" and sequelize-cli "^0.3.3". I just added foreign key constrain on my table using migration.createTable.
migration.createTable('order_items',{order_id: {references:"orders", "referencesKey": "id"}}). Both words have "s".

@corbanb Hmm, although the original issue deals with changeColumn not addColumn, so still might not work.

@mickhansen nope, changeColumn still doesn't work:

Executing (default): ALTER TABLE "Table" ALTER COLUMN "Column" TYPE UUID REFERENCES "OtherTable" ("uid") ON DELETE CASCADE ON UPDATE CASCADE;

SequelizeDatabaseError: syntax error at or near "REFERENCES"

Annoyingly this applies to any change to a column with a foreign key, not just addition/removal of a foreign key from a column.

So it's impossible to create allowsNull: false if your table already has rows. (Since you can't set it on addColumn since all rows in the table would violate the constraint and attempting to change it to addNull after filling up all the rows lands you in this issue).

Ok, I've come to a realization. Me and everyone else here are wrong.

Neither pg nor MySQL actually support REFERENCES in ALTER COLUMN. pg emits an error. MySQL may "say" it's valid syntax, but InnoDB actually ignores it.

You can modify a column that has a reference, all you do is exclude the reference information from the column options. The ALTER COLUMN operation does not modify the foreign key.

The proper way to modify foreign key references is using ADD [CONSTRAINT [symbol]] FOREIGN KEY ( column_name [, ... ] ) REFERENCES ... and DROP FOREIGN KEY (mysql) / DROP CONSTRAINT [ IF EXISTS ] constraint_name (pg).

So the real result for this bug should be:

• An extra set of migration functions should be added to handle references, something like addColumnReference / dropColumnReference.
• changeColumn should throw an error if the options contains references. Something like "reference cannot be used in changeColumn, use addColumnReference to add new foreign key references to a column".

Is there anyone working on a pull request for this, or should I work on a PR myself?

@legomind No work is currently being done, a PR would be great!

nothing yet?

+1

@corbanb Thanks for that code snippet. I tried to associate a new model with my User model, like you did with Post and it only worked when I changed User to the plural form "Users".
Is this the desired API? Because I flipped the table when I finally figured this out.

+1 still broken in ^3.12.1

Can anyone chime in with what dialects they had issues with specifically? We hit this in MySQL (and related issues in SQLite which has no alter table support). I'd like for a pull request to tackle each affected dialect.

@jocull All dialects fail. Constraints can't be added in a single add column call - So the logic needs to be changed to do two calls internally, or we add addConstraint methods as we've planned and force users to use that :)

I submitted pull request #5014 in an attempt to deal with this. Can anyone else help me finally fix this?

+1

Not sure if this should be reopened or if a new ticket should be made, but the constraint isn't properly removed when a migration undo is done:

module.exports = {
    up: function (queryInterface, Sequelize) {
        return queryInterface.changeColumn('access_tokens', 'user_id', {
            type: Sequelize.UUID,
            allowNull: Sequelize,
            field: 'user_id',
            references: {
                model: 'users',
                key: 'id'
            }
        })
    },

    down: function (queryInterface, Sequelize) {
        return queryInterface.changeColumn('access_tokens', 'user_id', {
            type: Sequelize.UUID,
            allowNull: Sequelize,
            field: 'user_id'
        })
    }
};

The up-migration here properly adds the keys, but the down migration doesn't remove them.

I have a same problem as @jamespedid. I use version 3.24.11 and mysql

@jamespedid open a new ticket

No need to open ticket @jamespedid , Its already in milestone v4 , #5212

@sushantdhiman I'm not sure if it solves my problem too. I have this code:

module.exports = {
  up: function(queryInterface, Sequelize) {
    return queryInterface.changeColumn('accounts', 'user_id', {
      type: Sequelize.INTEGER,
      onDelete: 'CASCADE',
      onUpdate: 'SET NULL'
    });
  },

  down: function(queryInterface, Sequelize) {
    return queryInterface.changeColumn('accounts', 'user_id', {
      type: Sequelize.INTEGER,
      onDelete: 'CASCADE',
      onUpdate: 'CASCADE'
    });
  }
};

Change is only on onUpdate from CASCADE to SET NULL, but after run sequelize db:migrate is created a new foreign key on user_id columns and old and wrong fk is still there

@Budry with #5212 you will be able to do that by pairing removeConstraint and addConstraint

@sushantdhiman thanks, you are right. Can you help me with this problem now? Exist any options how do this now? I can of course remove column and add again with correct properties, but I need keep data in table during migrations and this would be unpleasantly.

@Budry AFAIK no one is working on #5212, For now you can issue raw constraint change queries if you want to. Or you can help by working on #5212

@sushantdhiman thanks a lot.

After reading through this thread, it doesn't seem this has been implemented yet or am I incorrect?

@flouet-company should be implemented based on #7108