Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
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
- relates to
-
MDEV-24598 duplicate CHECK constraint name
-
- Stalled
-
Activity
Field | Original Value | New Value |
---|---|---|
issue.field.resolutiondate | 2018-07-01 21:13:22.0 | 2018-07-01 21:13:22.457 |
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 ] |
Link | This issue relates to MDEV-24598 [ MDEV-24598 ] |
Workflow | MariaDB v3 [ 88146 ] | MariaDB v4 [ 154595 ] |
Fixed with 8639e288086247ce39917f4cb55191c8bb5b5a8c