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

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.2, 10.3, 10.4, 10.5
    • Fix Version/s: 10.5.10
    • Component/s: Server
    • Labels:
      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

          Activity

            People

            Assignee:
            anel Anel Husakovic
            Reporter:
            serg Sergei Golubchik
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: