[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
----------------------------------
comments of functional spec/hard upgrade section:
It says:
During had upgrade existing backing indexes will be dropped and recreated as
almost unique indexes. It will be possible to create unique constraint over
nullable column in upgraded data base. After hard upgrade user will able to
create unique constraint over nullable columns and will also be able to drop
not null constraints even if the column is part of a unique constraint.
This is not what I expected and I believe is unnecessary and not a good idea.
Because the feature only affects constraints on
nullable columns which could never exist before the upgrade there should be
nothing necessary to drop/recreate. Once a hard
upgrade has happenned then the new backing index for unique constraint over
null columns will be enabled. Nothing should
"automatically" get dropped and recreated as an almost unique index.
Also there are still a number of gramatical and spelling errors in the
functional spec.
> 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-testcase.diff, derby-3330.diff,
> derby-3330v2.diff, derby-3330v3.diff, derby-3330v4.diff,
> FunctionalSpec_DERBY-3330.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.
