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

Cross-engine foreign keys support

Details

    Description

      Implement cross-engine foreign keys check at SQL layer.

      TODO:

      • Referenced/foreign key lookup procedure
      • Recursive table open (new FK structure for TABLE optimized for DML, FKs in TABLE point to parent TABLEs)
      • Recursive prelocking: write-locking for CASCADE actions
      • DML changes:
        UPDATE, Multi-UPDATE
        DELETE, Multi-DELETE
        REPLACE
        INSERT ODKU
        IGNORE clause
        Ignore ‘DELAYED’
      • DDL changes:
        DROP TABLE (DATABASE)

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17440 ON DELETE CASCADE does not always delete rows even if it could

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34403 Self-referencing table produces "Got error 193" from InnoDB on cascading DELETE

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

          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
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-17598 InnoDB index option for per-record transaction ID

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-20777 Foreign keys without indexes

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26554 Table-rebuilding DDL on parent table causes crash for INSERT into child table

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

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

          • Major - Major loss of function.
          • Open

          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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13538 better error reporting when FOREIGN KEY CONSTRAINT fails

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-22363 Reimplement the InnoDB virtual column code

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23716 FK validate data but in select join tables parent and child don't search data

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-26096 Constraints: support deferred constraints [WAS: Make the Unique index ONLY evaluate immediately before the commit (NOT after each UPDATE)]

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-26097 Constraints: support deferred constraints

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26675 Multiple Foreign Keys to same column and a multi-column index cause foreign key constraints to fail

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34403 Self-referencing table produces "Got error 193" from InnoDB on cascading DELETE

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

          Task - A task that needs to be done. MDEV-36348 Query Optimization for Counting Foreign Key Records Not Found in Parent Key even after adding indexes

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

          Web Link MySQL Bug#11472 Triggers not executed following foreign key updates/deletes

          Activity

            marko Marko Mäkelä added a comment -

            Implementing FOREIGN KEY processing in the SQL layer should also trivially fix MySQL Bug#11472 Triggers not executed following foreign key updates/deletes.
            The cause of the bug is that the InnoDB storage engine, which currently is responsible for enforcing FOREIGN KEY relationships, is executing ON DELETE or ON UPDATE clauses internally, without invoking any code outside the storage engine to execute any triggers.

            marko Marko Mäkelä added a comment - Implementing FOREIGN KEY processing in the SQL layer should also trivially fix MySQL Bug#11472 Triggers not executed following foreign key updates/deletes . The cause of the bug is that the InnoDB storage engine, which currently is responsible for enforcing FOREIGN KEY relationships, is executing ON DELETE or ON UPDATE clauses internally, without invoking any code outside the storage engine to execute any triggers.

            People

              Unassigned Unassigned
              midenok Aleksey Midenkov
              Votes:
              10 Vote for this issue
              Watchers:
              12 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.