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

A immediate Fk constraint blows up iff its referenced PK is deferred and we modify a duplicate key column

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

Details

    Description

      Similar to the issue in DERBY-6559, except here we modify the key in the referenced table. This leads Derby to check for any referencing FK and throw, even if there are other (formerly) duplicate rows that satisfy the FK constraint.

      Attachments

        1. derby-6576.diff
          14 kB
          Dag H. Wanvik
        2. derby-6576.status
          0.8 kB
          Dag H. Wanvik
        3. derby-6576-2.diff
          17 kB
          Dag H. Wanvik
        4. derby-6576-3.diff
          36 kB
          Dag H. Wanvik
        5. derby-6576-3.status
          1 kB
          Dag H. Wanvik
        6. derby-6576-cascade-setnull.diff
          85 kB
          Dag H. Wanvik
        7. derby-6576-cascade-setnull.status
          2 kB
          Dag H. Wanvik
        8. derby-6576-forbid-deferred+cascade-set-null-1.diff
          55 kB
          Dag H. Wanvik
        9. derby-6576-forbid-deferred+cascade-set-null-1.status
          2 kB
          Dag H. Wanvik
        10. derby-6576-repeatable-read.diff
          2 kB
          Dag H. Wanvik

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dagw Dag H. Wanvik
            dagw Dag H. Wanvik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment