Support CHECK constraint

[CbcWestwolf]

https://dev.mysql.com/doc/refman/8.0/en/create-table-check-constraints.html

[Benjamin2037]

Do we have same behavior as MySQL on check constraint?

[fzzf678]

Do we have same behavior as MySQL on check constraint?

Mostly same, I will supply unsupported behavior in doc later

[dveeden]

Looks like this has been implemented in v7.2. Can we close this issue?

mysql> SELECT TIDB_VERSION()\G
*************************** 1. row ***************************
TIDB_VERSION(): Release Version: v7.2.0
Edition: Community
Git Commit Hash: 9fd5f4a8e4f273a60fbe7d3848f85a1be8f0600b
Git Branch: heads/refs/tags/v7.2.0
UTC Build Time: 2023-06-27 15:04:42
GoVersion: go1.20.5
Race Enabled: false
Check Table Before Drop: false
Store: tikv
1 row in set (0.00 sec)

mysql> SET GLOBAL tidb_enable_check_constraint=ON;
Query OK, 0 rows affected (0.04 sec)

mysql> CREATE TABLE t1 (id INT PRIMARY KEY, CHECK (id > 10), CHECK (id < 20));
Query OK, 0 rows affected (0.20 sec)

mysql> INSERT INTO t1 VALUES (1);
ERROR 3819 (HY000): Check constraint 't1_chk_1' is violated.
mysql> INSERT INTO t1 VALUES (15);
Query OK, 1 row affected (0.02 sec)

mysql> INSERT INTO t1 VALUES (25);
ERROR 3819 (HY000): Check constraint 't1_chk_2' is violated.

[CbcWestwolf]

@dveeden Sure!

[shawn0915]

@CbcWestwolf could you help confirm is that a bug? #47567