[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anurag Shekhar updated DERBY-3330: ---------------------------------- Attachment: derby-3330v8.diff In this patch (derby-3330v8.diff) I have modified upgrade routine to upgrade only the backing indexes of unique constraint. Other indexes are left unchanged. DataDictionaryImpl.getAllConglomerates (introduced in derby-3330v6.dif) is no more required so I have taken it off. Tests are running without any error or failures. > provide support for unique constraint over nullable columns > ----------------------------------------------------------- > > Key: DERBY-3330 > URL: https://issues.apache.org/jira/browse/DERBY-3330 > Project: Derby > Issue Type: New Feature > Components: Store > Affects Versions: 10.4.0.0 > Environment: all > Reporter: Anurag Shekhar > Assignee: Anurag Shekhar > Attachments: BTreeController.diff, derby-3330-testcase.diff, > derby-3330.diff, derby-3330v2.diff, derby-3330v3.diff, derby-3330v4.diff, > derby-3330v5.diff, derby-3330v6.diff, derby-3330v7.diff, derby-3330v8.diff, > FunctionalSpec_DERBY-3330-V2.html, FunctionalSpec_DERBY-3330.html, > UniqueConstraint_Implementation.html > > > Allow unique constraint over nullable field. Right now derby support unique > constraint only over not null columns. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.