Seed bulkinsert requires createdAt, updatedAt by default (not documented)

[izznogooood]

What you are doing?

Creating seeds for cli created models.

'use strict';

module.exports = {
    up: (queryInterface, Sequelize) => {
        /*
      Add altering commands here.
      Return a promise to correctly handle asynchronicity.

      Example:
      return queryInterface.bulkInsert('People', [{
        name: 'John Doe',
        isBetaMember: false
      }], {});
    */
        return queryInterface.bulkInsert(
            'Languages',
            [
                {
                    id: 1,
                    name: 'english',
                    createdAt: new Date(),
                    updatedAt: new Date()
                },
                {
                    id: 2,
                    name: 'norwegian',
                    createdAt: new Date(),
                    updatedAt: new Date()
                }
            ],
            {}
        );
    },
    
    down: (queryInterface, Sequelize) => {
        /*
      Add reverting commands here.
      Return a promise to correctly handle asynchronicity.

      Example:
      return queryInterface.bulkDelete('People', null, {});
    */
    }
};

What do you expect to happen?

Expeted to work like the examples (without createdAt, updatedAt)

What is actually happening?

Need createdAt, updatedAt.

Output, either JSON or SQL

Dialect: sqlite / postgres
Database version: 3 / 10.3
Sequelize CLI version: 5.4.0
Sequelize version: 5.8.7

Suggestion

If you want I could update the docs to reflect this?
/ or
Take a stab at adding this automatically.

[eugene-matvejev]

when you define models, you can use timestamps: false, may be that is what you are looking for?
eugene-matvejev/node-battleship#1

[izznogooood]

Yes and no, I found that option later. Adding the timestamps to the documentation would save me the troubleshooting when following the documentation.

Or, implement automatic actions to create/update this in db:seed

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ShaharHD]

#899 should resolve this once approved and merged.

[sushantdhiman]

Fixed by #899