CODEWITHSUNDEEP
mysqlsequelize.js
proteus
proteus

Reputation: 505

Not store updatedAt with sequelize model

When I store models in my MySQL DB, they are immutable. As a result I can see the need for the createdAt column in my tables, but I don't need the redundant updatedAt column. Can I configure sequelize not to store updatedAt time and then can I drop the column from my table?

Upvotes: 3

Views: 3673

Answers (2)

aug
aug

Reputation: 11714

Looking at the documentation regarding your situation

If you want sequelize to handle timestamps, but only want some of them, or want your timestamps to be called something else, you can override each column individually:

const Foo = sequelize.define('foo',  { /* bla */ }, {
  // don't forget to enable timestamps!
  timestamps: true,

  // I don't want createdAt
  createdAt: false,

  // I want updatedAt to actually be called updateTimestamp
  updatedAt: 'updateTimestamp',

  // And deletedAt to be called destroyTime (remember to enable paranoid for this to work)
  deletedAt: 'destroyTime',
  paranoid: true
})

So in the above example, just set timestamps to be true but then createdAt to be false

Upvotes: 6

proteus
proteus

Reputation: 505

Found my own answer at http://docs.sequelizejs.com/manual/tutorial/models-definition.html#configuration, I should use updatedAt: false in my model definition.

Upvotes: 2

Related Questions