Also managed to reproduce this one. It does not seem to be just the case of incorrect exception type - in our case the column name used in @UniqueConstraint seems to be fine (a field with the same name exists in the entity) and the same code works on 4.2.5. Seems to be a regression in 4.2.6.
|