Home/ Questions/Q 864513
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T09:29:27+00:00

Lets say UserA and UserB both have an application open and are working with

  • 0

Lets say UserA and UserB both have an application open and are working with the same type of data. UserA inserts a record into the table with value 10 (PrimaryKey=’A’), UserB does not currently see the value UserA entered and attempts to insert a new value of 20 (PrimaryKey=’A’). What I wanted in this situation was a DBConcurrencyException, but instead what I have is a primary key violation. I understand why, but I have no idea how to resolve this. What is a good practice to deal with such a circumstance? I do not want to merge before updating the database because I want an error to inform the user that multiple users updated this data.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What I wanted in this situation was a DBConcurrencyException, but instead what I have is a primary key violation. I understand why

    This is the correct Exception for this situation. You say you want to inform the user that this value has already been inserted so just catch the Primary key exception and then spit the user-friendly message back.

    • 0