Allow foreignKey field name and column name definition

What you are doing?

When association is defined like below sequelize will expect column with name ‘image_type_id’ to exists in the ‘image’ table and will add a field in the Image model instance with name ‘image_type_id’.

Image.belongsTo(ImageType, {
    foreignKey: {
        name: 'image_type_id'
    },
    as: 'imageType'
});

What do you expect to happen?

I would like to be able to separately define model filed name and table column name, so that I do not have to use snake case column names in sequelize queries.

What is actually happening?

The name of the model field is ‘image_type_id’ instead of ‘imageTypeId’.

Something like would be ok:

Image.belongsTo(ImageType, {
    foreignKey: {
        name: 'image_type_id',
        fieldName: 'imageTypeId'
    },
    as: 'imageType'
});

Dialect: postgres Database version: 9.4.4 Sequelize version: 3.23.3

[ssljivic]

It should be mapped like this:

sequelize.define('Image', {
    id: {
        field: 'image_id',
        type: DataTypes.BIGINT,
        allowNull: false,
        primaryKey: true,
        autoIncrement: true
    },
    //...
    imageTypeId: {
        field: 'image_type_id',
        type: DataTypes.BIGINT
    }
}, {
    tableName: 'image',
    classMethods: {
        associate: function (models) {
            models.Image.belongsTo(models.ImageType, {
                foreignKey: {
                    fieldName: 'imageTypeId'
                },
                as: 'imageType'
            });
        }
    }
});

Thanks @mickhansen .

[weldermarcosxd]

@ssljivic how that association would be defined in ImageType side, Im getting ‘model is not associated with model2’ no matter hard I try, Thank you.