As others have mentioned that there are two possible approaches, one is to test and then insert/update otherwise handle SQL Exception. Both these approaches have their downsides:
- Caveat for "Test before inserting" is that every
transaction will have additional queries which will impact performance. This is specially a bigger issue when such erroneous transactions are few in number.
- Caveat for "Evaluating SQL Exception" is that such
exception messages are very database specific. These messages, most of the time, don't
give specific information beyond stating that there is constrain violation.
So, I will propose an approach which is hybrid of the two.
- Don't perform the test before insert.
- Let database throw an
exception.
- Catch SQL Exception.
- In the exception flow (catch
block), do additional queries to form very specific error messages to
indicate customers what has exactly failed (unique key, primary key,
foreign key, specific columns etc).
This may require few additional lines of code but it definitely improves performance and generates friendly error messages.