db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected
Date Thu, 06 Mar 2008 14:08:58 GMT
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


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