Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

paranoid is not working with underscored option

See original GitHub issue

What are you doing?

Destory instance with paranoid and underscored. After update deleted_at column(db), sequelize does not map to deletedAt field(instance).

What do you expect to happen?

brand.destory();

brand {
  dataValues:
   { id: '16',
     updatedAt: '2019-03-16T11:01:19.633Z',
     createdAt: '2019-03-16T10:47:23.738Z',
     deletedAt: '2019-03-16T11:01:43.930Z'
   },
  _previousDataValues:
   { id: '16',
     deletedAt: null,
     createdAt: '2019-03-16T10:47:23.738Z',
     updatedAt: '2019-03-16T11:01:19.633Z' }

What is actually happening?


brand {
  dataValues:
   { id: '16',
     updatedAt: '2019-03-16T11:01:19.633Z',
     createdAt: '2019-03-16T10:47:23.738Z',
     deletedAt: null,
     deleted_at: '2019-03-16T11:01:43.930Z'
   },
  _previousDataValues:
   { id: '16',
     deletedAt: null,
     createdAt: '2019-03-16T10:47:23.738Z',
     updatedAt: '2019-03-16T11:01:19.633Z' }

Dialect: postgres Sequelize version: 5.1.0 Tested with latest release: Yes

Note : Your issue may be ignored OR closed by maintainers if it’s not tested against latest version OR does not follow issue template.

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

KristenKatonacommented, Mar 26, 2019

My team is also experiencing the issue and we’ve done a workaround by creating a base model that all of our paranoid delete models extend. In that base model we added a hook for afterDestroy that simply renames the deleted_at field to deletedAt.

0reactions

papbcommented, Aug 20, 2019

Closing in favor of #11225