[MDEV-24601] INFORMATION_SCHEMA doesn't differentiate between column- and table-level CHECK constraints Created: 2021-01-15  Updated: 2021-03-16  Resolved: 2021-03-16

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.5.10

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Anel Husakovic
Resolution: Fixed Votes: 1
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.

 Comments   
Comment by Anel Husakovic [ 2021-03-02 ]

Hi wlad, serg can you please review patch 2784900c4b4cf6

Comment by Anel Husakovic [ 2021-03-03 ]

Hi wlad, is the review finished, just to drop binlog results not related to change?
Regarding realistic test case, I needed just to way to check for field/table constraints, and used ints for that purpose.

Comment by Anel Husakovic [ 2021-03-16 ]

Hi wlad. I have updated the patch with 8189b706. Here is the buildbot, where single failure in ps-protocol I'm not sure about>
ps-protocol-test-case-innodb.innodb_stats (locally it is working innodb.innodb_stats ).
Can you please confirm this so I can push?

Comment by Vladislav Vaintroub [ 2021-03-16 ]

anel, this looks good to me. I guess you can push. Ignore innodb_stats failure, that single sporadic failure is not your fault.

Comment by Anel Husakovic [ 2021-03-16 ]

Pushed to 10.5 with commit 825c0e2ab. Thanks wlad.

Generated at Thu Feb 08 09:31:13 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.