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

INFORMATION_SCHEMA doesn't differentiate between column- and table-level CHECK constraints

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.5, 10.2(EOL), 10.3(EOL), 10.4(EOL)
    • 10.5.10
    • Server
    • None

    Description

      perhaps an appropriate I_S.check_constraints table needs a column, like LEVEL ENUM('COLUMN','TABLE') or a column COLUMN with the column name of the constraint or NULL for table-level constraints.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24598 duplicate CHECK constraint name

          • Major - Major loss of function.
          • Stalled

          Activity

            People

              anel Anel Husakovic
              serg Sergei Golubchik
              Votes:
              1 Vote for this issue
              Watchers:
              6 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.