Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3502

Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 10.4.1.3
    • Fix Version/s: 10.4.1.3
    • Component/s: SQL
    • Labels:
      None

      Description

      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.

        Attachments

        1. derby-3502v1.diff
          10 kB
          Anurag Aggarwal
        2. derby-3502v2.diff
          9 kB
          Anurag Aggarwal
        3. derby-3502v3.diff
          14 kB
          Anurag Aggarwal
        4. d3502v3_modified_1.diff
          14 kB
          A B

        Issue Links

          Activity

            People

            • Assignee:
              anurag Anurag Aggarwal
              Reporter:
              anurag Anurag Aggarwal

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment