[MDEV-17180] Adding a CHECK() constraint apparently failed silently Created: 2018-09-12 Updated: 2020-08-25 Resolved: 2018-12-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Triggers |
| Affects Version/s: | 10.2.11 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Adding check constraints to a large partitioned table silently failed. ALTER TABLE didn't return an error, but the CHECK constraints are clearly not there. When doing tests with a table using exactly the same schema, and randomly generated data of about the same two digit gigabyte size this is not reproducible. |
| Comments |
| Comment by Hartmut Holzgraefe [ 2018-09-12 ] | |||
|
Could this maybe be caused by the table originally having been created using an older version than 10.2? | |||
| Comment by Elena Stepanova [ 2018-10-03 ] | |||
|
We need some evidence of it actually happening as described, e.g. an unabridged copy-paste or screenshot of
| |||
| Comment by Hartmut Holzgraefe [ 2018-12-17 ] | |||
|
We now have confirmation that ALTER indeed failed with an error after the SSH disconnect. The error message is just a generic "Constraint failed", so we still don't know the root cause, but this bug report can surely be closed now. |