Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1581994883.1204835698282.JavaMail.jira@brutus>
Date: Thu, 6 Mar 2008 12:34:58 -0800 (PST)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3330) provide support for unique constraint
 over keys that include one or more nullable columns.
In-Reply-To: <8759495.1200598893963.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Matrigali updated DERBY-3330:
----------------------------------

    Attachment: derby-3330_followup_1_modified.diff

Here is the modified followup patch that I am looking at committing if it passes tests - tests running now.  It has all your followup changes except the sorter changes.  It has some spelling/comment fixes also.  
If no other problems are found with existing sorter implementation I am ok leaving it for now the way it is, if there are new problems I think the sort observer solution is cleaner for the future.

If you have some added comments for the sorter file just submit them as a separate patch, and I can commit those easily without worrying about test running.

> 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-3330_followup_1.diff, derby-3330_followup_1_modified.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, UniqueConstraint_Implementation_V4.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.