Home/ Questions/Q 7820593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T07:21:25+00:00

I have a unique constraint on a Navigations table’s column called Index . I

  • 0

I have a unique constraint on a Navigations table’s column called Index. I have two Navigation entities and I want to swap their Index values.

When I call db.SaveChanges it throws an exception indicating that a unique constraint was violated. It seems EF is updating one value and then the other, thus violating the constraint.

Shouldn’t it be updating them both in a transaction and then trying to commit once the values are sorted out and not in violation of the constraint?

Is there a way around this without using temporary values?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It is not problem of EF but the problem of SQL database because update commands are executed sequentially. Transaction has nothing to do with this – all constrains are validated per command not per transaction. If you want to swap unique values you need more steps where you will use additional dummy values to avoid this situation.

    • 0