|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I just discovered that a table contains dozends of unique constraints - randomly named and generated by hibernate at each startup. I guess this is the reason why it would be better to use non-random constraint names - correct? So, hopefully this problem will dissappear in 4.2.2.
What remains is cleaning up the database...