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

Clarify how DROP statements work on trigger dependencies

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

Details

    Description

      Some of the DROP statement topics don't mention what happens if an object depended on by a trigger gets dropped. We should add this information. The behaviour should be more consistent after DERBY-2041.

      Attachments

        1. rrefsqljdropsynonym.html
          5 kB
          Camilla Haase
        2. DERBY-6420-3.diff
          0.6 kB
          Camilla Haase
        3. DERBY-6420-2.zip
          11 kB
          Camilla Haase
        4. DERBY-6420-2.diff
          5 kB
          Camilla Haase
        5. DERBY-6420.zip
          11 kB
          Camilla Haase
        6. DERBY-6420.stat
          0.2 kB
          Camilla Haase
        7. DERBY-6420.diff
          6 kB
          Camilla Haase

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. DERBY-2041 Trigger should register a dependency on tables and columns used in its body

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

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

          People

            chaase3 Camilla Haase
            knutanders Knut Anders Hatlen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment