db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (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 22:37:46 GMT

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

A B updated DERBY-3502:

    Attachment: d3502v3_modified_1.diff

I tweaked the v3 patch slightly by:

  a) Adding more comments to CreateIndexConstantAction in hopes of making the
    "share" condition more clear.

  b) Changed the name and javadoc of the new test fixture in ConglomerateSharingTest
    to more closely reflect what the fixture is testing.

  c) Some minor formatting cleanup to keep lines under 80 chars.

All code changes should be the same as v3.  I committed the modified patch, d3502v3_modified_1.diff,
with svn # 634852:

  URL: http://svn.apache.org/viewvc?rev=634852&view=rev

Thanks for addressing this so quickly, Anurag.

> Unique Constraint's backing index when shared with existing indexes doesn't behave as
> ----------------------------------------------------------------------------------------------
>                 Key: DERBY-3502
>                 URL: https://issues.apache.org/jira/browse/DERBY-3502
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Anurag Shekhar
>            Assignee: Anurag Shekhar
>            Priority: Critical
>             Fix For:
>         Attachments: d3502v3_modified_1.diff, derby-3502v1.diff, derby-3502v2.diff, derby-3502v3.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.

View raw message