Skip to content

Conflict on insert gets translated to DataIntegrityViolationException instead of DuplicateKeyException in Spring 6 #29699

New issue
New issue
Closed
Closed
Conflict on insert gets translated to DataIntegrityViolationException instead of DuplicateKeyException in Spring 6#29699
Assignees
jhoeller
Labels
in: dataIssues in data modules (jdbc, orm, oxm, tx)type: regressionA bug that is also a regression
Milestone
6.0.4
@lukas-krecan

Description

@lukas-krecan
lukas-krecan
opened on Dec 16, 2022

Followup from #29511

If there is primary key conflict on insert, Spring 6.0.3 returns DataIntegrityViolationException instead of DuplicateKeyException as it did in Spring 5. It would make sense to me to implement similar fix as you did for #29511. The SQL state seems to be 23000.

Metadata

Metadata

Assignees

Labels

in: dataIssues in data modules (jdbc, orm, oxm, tx)type: regressionA bug that is also a regression

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions