Something like this won't be possible until HHH-8380 is investigated. There's not currently a reliable way to identify existing unique constraints in JDBC. See the discussion on HHH-8380.
The schema validator currently only checks that the columns in the persistence store exist and have the correct data types. I'm not sure if it's a bug or intended behavior (in which case this would be an enhancement), but the validator doesn't check that indices and unique keys also exist (with the correct names referring to the correct columns).
I've at...
This message was sent by Atlassian JIRA (v6.1-OD-09-WN#6144-sha1:62dfc48)