Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <419916469.1206714384599.JavaMail.jira@brutus>
Date: Fri, 28 Mar 2008 07:26:24 -0700 (PDT)
From: "Anurag Shekhar (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3474) update unique constraint sections of
 refrence manual
In-Reply-To: <960489152.1204113591433.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-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583042#action_12583042 ] 

Anurag Shekhar commented on DERBY-3474:
---------------------------------------

There was a minor change in implementation since I created this issue. 
The backing index for unique constraint can be either unique index (if all the columns are non null able) or a non unique index (if one or more columns are null able) 

rrefsqlj13590.html should explain this. Rest of the changes looks fine to me.

> update unique constraint sections of refrence manual
> ----------------------------------------------------
>
>                 Key: DERBY-3474
>                 URL: https://issues.apache.org/jira/browse/DERBY-3474
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.4.0.0
>            Reporter: Anurag Shekhar
>            Assignee: Kim Haase
>         Attachments: DERBY-3474-2.diff, derby-3474.diff, rrefsqlj13590.html, rrefsqlj81859.html
>
>
> Derby-3330 adds support for unique constraint over null able fields. Derby refrence manual should be updated to include it while explaining about unique constraint.

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