|
||||||||
|
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 |
||||||||
zhouyanming, this is no different than what you wrote in
HHH-8205. We switched to using randomly generated names for a good reason – to ensure that generated names do not go past the 30 character limit that a few dialects enforce. SeeHHH-1904.Further, UniqueConstraints were not originally generated by SchemaUpdate. At all. So, if you want the original functionality, switch to using the SKIP strategy.
If you want to continue to allow SchemaUpdate to generate UniqueConstraints, your issue is easily overcome by explicitly naming the constraints.