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] Commented: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected
Date Thu, 06 Mar 2008 18:22:58 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575821#action_12575821

A B commented on DERBY-3502:

Have yet to review the engine changes, but re: the testing:

  1) There is an existing test, lang/ConglomerateSharingTest.java, that exists for testing
situations where constraints and/or indexes share a conglomerate.  Might be better to add
your new test cases to that class instead of creating an entirely new test?

  2) The new test fixtures do not close the statements they create, which may interfere with
other tests when run as part of suites.All (unless something has been done to fix that lately...?).
 Also, when moving the tests to ConglomerateSharingTest.java, it might be good to use that
class's utility methods to confirm that conglomerate sharing is (or is not) happening as expected--esp.
count the number of conglomerates before/after the statements of interest.  See existing test
fixtures in ConglomerateSharingTest.java for examples...

> 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
>         Attachments: derby-3502v1.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