db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected
Date Fri, 07 Mar 2008 05:28:57 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-3502:
----------------------------------

    Priority: Critical  (was: Major)

bumping priority, i don't think 10.4 should go out with the new constraint feature without
these issues resolved as it 
can lead to constraint failures and incorrect behavior of other pre-existing indexes.

> Unique Constraint's backing index when shared with existing indexes doesn't behave as
expected
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3502
>                 URL: https://issues.apache.org/jira/browse/DERBY-3502
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.4.0.0
>            Reporter: Anurag Shekhar
>            Assignee: Anurag Shekhar
>            Priority: Critical
>         Attachments: derby-3502v1.diff, derby-3502v2.diff
>
>
> Unique Constraint now uses non unique backing indexes with new attribute UniqueWithDuplicateNulls.
This index has following sharing properties
> 1. Can use an existing unique index.
> 2. Non Unique indexes (and foreign key) can use this index.
> While dropping a unique index a new index for unique constraint should be created.
> when a unique constraint is dropped a new index for a non unique index or foreign key
should be created. 
> Army has found several issues in actual behavior. This problems are listed in DERBY-3456.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message