|
||||||||
|
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 went with the "UniqueDelegate" idea. However, the delegate ended up being more complicated. With AST, 1 "applyUniqueness" method might be possible. But due to .cfg and .mapping still resolving around StringBuilders, separate methods were needed.
The default delegate creates unique constraints in separate "alter table" statements. After auditing the other DBs and running my changes through the master-matrix CI job, DB2 is the only dialect that needed changes. There, if a column is nullable and unique, a unique index must be used in place of a constraint. Other than that, all other dialects appear to work with the constraints.