postgresql - Sequelize.js model.save() method is not throwing ValidationError - Stack Overflow

I use the following function in an API I am building

const editUserInfo = catchAsync(async(req, res, next) => {
    const userId = req.user.id;
    const body = req.body;
    const result = await user.findByPk(userId);

    result.userName = body.userName;
    result.email = body.email;

    const updatedResult = await result.save();
    console.log(updatedResult.toJSON())
...

The username and email fields of my model are identified as unique in both the model definitions and the migrations file, and I have verified that the Database is constraining them as unique. The catchAsync wrapper function should be catching the validation error, and does so when I attempt to create() new instances that violate the constraints.

However, in this function, despite result.save() never sending an UPDATE query to my DB, updatedResult is set to the original model, and no error is reported.

For example, when

{
  username: 'JWick',
  email: '[email protected]',
}

is sent, despite JWick already existing in the database, the function reports a success code while not actually sending the update to the DB

I would hope that it would report an error so that the API can tell the front-end that the operation failed, but I'm not sure how to go about that

I use the following function in an API I am building

const editUserInfo = catchAsync(async(req, res, next) => {
    const userId = req.user.id;
    const body = req.body;
    const result = await user.findByPk(userId);

    result.userName = body.userName;
    result.email = body.email;

    const updatedResult = await result.save();
    console.log(updatedResult.toJSON())
...

The username and email fields of my model are identified as unique in both the model definitions and the migrations file, and I have verified that the Database is constraining them as unique. The catchAsync wrapper function should be catching the validation error, and does so when I attempt to create() new instances that violate the constraints.

However, in this function, despite result.save() never sending an UPDATE query to my DB, updatedResult is set to the original model, and no error is reported.

For example, when

{
  username: 'JWick',
  email: '[email protected]',
}

is sent, despite JWick already existing in the database, the function reports a success code while not actually sending the update to the DB

I would hope that it would report an error so that the API can tell the front-end that the operation failed, but I'm not sure how to go about that

• postgresql
• sequelize.js

Share Follow asked Jan 31 at 5:07 Logan GoswickLogan Goswick 1 1

• Check for logging to see if the update query is even being executed. new Sequelize(... logging: console.log // Log all queries to the console }); – Arun kumar Commented Jan 31 at 5:28

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Catch SequelizeUniqueConstraintError explicitly to handle constraint violations