[
https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3456:
----------------------------------
Attachment: derby-3456v4.diff
This patch fixes issues related to unique constraint using
existing non unique index as backing index (see Army's comments issues 1).
I have updated lterTableConstantAction.java to check for
uniqueWithDuplicateNulls while deciding whether to share existing index or not.
In case there is a uniqueWithDuplicateNulls index it can be used by a non
unique index but not vice-versa.
I am investigating other two issues.
> Allow removing not null from collumns particpating in unique constraint.
> ------------------------------------------------------------------------
>
> Key: DERBY-3456
> URL: https://issues.apache.org/jira/browse/DERBY-3456
> Project: Derby
> Issue Type: Sub-task
> Components: SQL, Store
> Affects Versions: 10.4.0.0
> Environment: all
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: altertable.diff, derby-3456-Tests.diff,
> derby-3456v1.diff, derby-3456v2.diff, derby-3456v3.diff, derby-3456v4.diff,
> setnulltest.diff, upgradetests.diff, upgradetests_v2.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
