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] Updated: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.
Date Wed, 05 Mar 2008 07:55:40 GMT

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

Anurag Shekhar updated DERBY-3330:
----------------------------------

    Attachment: derby-3330-UpgradeTests.diff

description of derby-3330-UpgradeTests.diff 

This patch has following tests

tests for unique constraint
1. Create a unique constraint in lower version of derby
2. Test the above constraint in soft upgrade mode.
3. create a new unique constraint in soft upgrade mode.: Shouldn't able to create   
    unique constraint over nullable columns.
4. test the above constraint in post soft upgrade mode (running under lower version)

tests for index
This test is for indexes in different modes. Different types are indexes are created 
during
1. Create (running under older version)
2. Soft Upgrade mode
3. Post soft upgrade mode 
4. Hard upgrade mode

In all these phases the indexes created in previous phases are tested.

The types of indexes created in each phases are 
1. Unique index over not null field
2. Unique Index over null able field
3. Non Unique constraint over not null field
4. Non Unique constraint over null able field.

> provide support for unique constraint over keys that include one or more 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: BTreeController.diff, db2Compatibility-v2.diff, db2Compatibility.diff,
derby-3330-testcase.diff, derby-3330-UpgradeTests.diff, derby-3330.diff, derby-3330v10.diff,
derby-3330v11.diff, derby-3330v12.diff, derby-3330v13.diff, derby-3330v2.diff, derby-3330v3.diff,
derby-3330v4.diff, derby-3330v5.diff, derby-3330v6.diff, derby-3330v7.diff, derby-3330v8.diff,
derby-3330v9.diff, derbyall_report.txt, FunctionalSpec_DERBY-3330-V2.html, FunctionalSpec_DERBY-3330.html,
UniqueConstraint_Implementation.html, UniqueConstraint_Implementation_V2.html, UniqueConstraint_Implementation_V3.html
>
>
> Allow unique constraint over keys which include one or more nullable fields.  Prior to
this change Derby only supported unique constraints on keys that included no nullable columns.
 The new constraint will allow unlimited inserts of any key with one more null columns, but
will limit insert of keys with no null columns to 1 unique value per table.
> There is no change to existing or newly created unique indexes on null columns (as opposed
to unique constraints on null columns).  Also there is no change to existing or newly created
constraints on keys with no nullable columns.

-- 
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