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

Support CHECK constraint as in (or close to) SQL Standard

Details

    Description

      Support CHECK constraint as in (or close to) SQL Standard.

      The following syntaxes will be supported (they are already supported by the current MariaDB parser, but does nothing):

      As part of column definition:
      CREATE TABLE t1 (a int check (A > 10));

      As an independent constraint:
      CREATE TABLE t1 (a int, constraint `A` CHECK (A > 10));

      ALTER TABLE DROP CONSTRAINT `A`;

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16331 Support instant DROP CHECK CONSTRAINT

          • Major - Major loss of function.
          • Closed
          is part of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-10137 Providing compatibility to other databases

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11114 Cannot drop column referenced by CHECK constraint

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11115 CHECK constraints are not shown in I_S.TABLE_CONSTRAINTS

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11117 CHECK constraint fails on intermediate step of ALTER

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12890 constraint name in column constraints

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

          Task - A task that needs to be done. MDEV-17323 Backport INFORMATION_SCHEMA.CHECK_CONSTRAINTS to 10.2

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13596 CHECK constraints disallow NULL to pass through, violating SQL

          • Major - Major loss of function.
          • Closed

          Activity

            Descending order - Click to sort in ascending order
            monty Michael Widenius added a comment -

            This is now available in bb-10.2-default branch. Will be pushed into 10.2.1 shortly.
            It's already documented at https://mariadb.com/kb/en/mariadb/create-table/

            monty Michael Widenius added a comment - This is now available in bb-10.2-default branch. Will be pushed into 10.2.1 shortly. It's already documented at https://mariadb.com/kb/en/mariadb/create-table/
            serg Sergei Golubchik added a comment -

            Yes, there are plans to do it. But at the moment there's nothing final yet. Ask in a few weeks, please.

            serg Sergei Golubchik added a comment - Yes, there are plans to do it. But at the moment there's nothing final yet. Ask in a few weeks, please.
            Manasa ManasaTulluri added a comment - - edited

            Hi Dev Team,

            Kindly let us know if you are implementing check constraints any time soon in the up coming releases.

            Please let us know tentative date. We are migrating from Oracle to Mariadb and this will be very handy for us.

            Thanks & Regards,
            Manasa Tulluri.

            Manasa ManasaTulluri added a comment - - edited Hi Dev Team, Kindly let us know if you are implementing check constraints any time soon in the up coming releases. Please let us know tentative date. We are migrating from Oracle to Mariadb and this will be very handy for us. Thanks & Regards, Manasa Tulluri.
            laurent.langlois Laurent Langlois added a comment -

            This issue if also of rather high priority for me.

            We are in the process of migrating databases from Sybase to MariaDB and our database makes extensive use of Sybase "rules." From what I know, it would seem that to implement the equivalent, 'check constraint' would be much easier to use (implement, maintain, etc.) than triggers.

            laurent.langlois Laurent Langlois added a comment - This issue if also of rather high priority for me. We are in the process of migrating databases from Sybase to MariaDB and our database makes extensive use of Sybase "rules." From what I know, it would seem that to implement the equivalent, 'check constraint' would be much easier to use (implement, maintain, etc.) than triggers.
            toddmallen Todd Allen added a comment -

            I would also very much like to see this implemented.

            toddmallen Todd Allen added a comment - I would also very much like to see this implemented.
            libcub Paul Weiss added a comment -

            This one is very high priority for me.

            libcub Paul Weiss added a comment - This one is very high priority for me.

            People

              monty Michael Widenius
              serg Sergei Golubchik
              Votes:
              11 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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