Subclass DataIntegrityViolationException to represent main constraint types and translate SQL exceptons into appropriate subclass [SPR-2977]

[spring-projects-issues]

Oleksandr Alesinskyy opened SPR-2977 and commented

To the moment any SQL constraint violation exception is translated into generic DataIntegrityViolationException. It would be nice to have special subclasses for different constraint types - uniqueness violation, referential integrity violation, check violation (check constraint imposes restriction on fields of the same record). This conception is mostly rlational, but, first of all, most of databases in use are relational, and, secondly, at least conception of uniqueness and check are applicable to another database types. Referential integrity often may be interpreted in some way for non-relational databases as well.

Unlike inclusion of constraint name, which is almost impossible for techical reasons (different DBMS represent them in different ways), inclusion of constraint type shall be more or less straitforward, as virtually all DBMS report them by different values of sql error code/sql state. These values are more or less standartized, while there are several flavours.

There is a good reason to implement this functionality - constraint violation errors ususally are not fatal, application may recover (alone or with user interaction) . Direct analyse of SQL error code by application will make application too dependent on specific DB, so this translation will be of great use.

Regards,
Oleksandr

---

Affects: 2.0.1

Issue Links:

• Add DuplicateKeyException to DAO exception hierachy [SPR-5125] #9798 Add DuplicateKeyException to DAO exception hierachy

3 votes, 2 watchers

[spring-projects-issues]

Oleksandr Alesinskyy commented

Any progress on this issue?

[spring-projects-issues]

Rick Evans commented

Sounds like a good enhancement to me.

+1

I have voted for it... Thomas (Risberg) and Juergen are the arbiters of the Spring data access modules though, so hopefully my commenting on this issue and bumping it to the top of the most recently updated list will get some comment.

Cheers
Rick

[spring-projects-issues]

Thomas Risberg commented

Partially resolved in #9798 Add DuplicateKeyException to DAO exception hierachy

Did not include separate check constraint exception since I did not see great value in this as a separate exception class.

[spring-projects-issues]

Oleksandr Alesinskyy commented

And what for referential integrity- it definitely deserves a separate class as in many cases application can perform some alternative actions.