The issue is compounded because for some reason the names of the primary key indexes are "PRIMARY_KEY_X" where X is some alphanumeric char, instead of using the constraint name that was specified.
For any other constraints, it uses ConstraintName_INDEX_X. On Sep 4, 10:22 pm, Caleb <[email protected]> wrote: > It seems that constraint violation errors return the index name > instead of the real constraint name, for example: "Unique index or > primary key violation: "UK_TEST_FOO_INDEX_7 ON ........" > > I'd really like to use the constraint names to give more meaningful > messages in my application (using Hibernate). Is there any reason why > the index name is used? > > Thanks! -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
