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

Ambiguous error message when check constraint matches table name

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 10.2.17, 10.3.9
    • Server
    • None

    Description

      We currently have 2 types of check constraints.

      Field check constraints and table check constraints. If a column with a check constraint has the same name as a table check constraint for the same table, it is impossible to tell which check constraint failed.

      create table test.t(a int, b int check(b>0),
                          constraint b check(a<b));
      

      For either of the checks in the above table, the error message is:

      CONSTRAINT b failed for test.t
      

      Attachments

        Issue Links

          Activity

            cvicentiu Vicențiu Ciorbaru created issue -
            anel Anel Husakovic added a comment - Fixed with 8639e288086247ce39917f4cb55191c8bb5b5a8c
            anel Anel Husakovic made changes -
            Field Original Value New Value
            issue.field.resolutiondate 2018-07-01 21:13:22.0 2018-07-01 21:13:22.457
            anel Anel Husakovic made changes -
            Fix Version/s 10.2.17 [ 23111 ]
            Fix Version/s 10.3.9 [ 23114 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            anel Anel Husakovic made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 88146 ] MariaDB v4 [ 154595 ]

            People

              anel Anel Husakovic
              cvicentiu Vicențiu Ciorbaru
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.