[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
----------------------------------
Attachment: derby-3330v2.diff
I have done some cleanup in this patch. This patch also includes fixes based on
the failures in regression tests. I still have failures in regression tests. I
will posting another patch after fixing them.
This patch has following changes since the last time.
1. Modified IndexRowGenerator to keep the information if this represents an
almost unique index. This information is used by IndexChanger to deffer the
inserts for update in case of almost unique index (in addition to unique index).
2. Modified BTreeControler.compareLeftAndRightSiblings to use newly introduced
methods to get the record at left and right. These two methods check for
deleted record and continue to move to previous (in case of right next) record
till it finds a valid record.
I have also identified the code changed required for soft upgrade (marked with
comments)
> 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: derby-3330.diff, derby-3330v2.diff
>
>
> 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.
