Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10393

Foreign keys SET DEFAULT action

Details

    Description

      Now that the DEFAULT clause has been greatly improved (10.2), it would be desirable to be able to used the SET DEFAULT action in foreign keys:
      ON DELETE SET DEFAULT
      ON UPDATE SET DEFAULT

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. MDEV-20480 Obsolete internal parser for FK in InnoDB

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-31942 Online alter: support cascade foreign keys

          • Major - Major loss of function.
          • Open
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-16417 Store Foreign Key metadata outside of InnoDB

          • Critical - Crashes, loss of data, severe memory leak.
          • In Review

          New Feature - A new feature of the product, which has yet to be developed. MDEV-12483 Add foreign keys support for partitioned tables

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled

          Activity

            marko Marko Mäkelä added a comment -

            I think that this would be easiest to implement by moving both the FOREIGN KEY metadata storage and processing entirely out of InnoDB.

            marko Marko Mäkelä added a comment - I think that this would be easiest to implement by moving both the FOREIGN KEY metadata storage and processing entirely out of InnoDB.

            People

              midenok Aleksey Midenkov
              f_razzoli Federico Razzoli
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.