Appling Applying @Column(unique = true) doesn't lead to an unique constraint being created at database level.
I'd consider this bug critical since it fails silently and therefore leads to database corruption. The test data I used was scenario happens when adding an unique therefore there should have been no reason for not applying the unique constraint
The issue happens on an already existing table, however, after doublechecking, the content multiple fields individually and one of the database was containing only unique entries, therefore it should them does not have been possible unique fields. This leads to apply potential silent data corruption and a constant need to doublecheck the constraint application since due to [https://hibernate . atlassian.net/browse/HHH-11813|https://hibernate.atlassian.net/browse/HHH-11813|smart-link] it’s not reported at all at application level.
|
|
