Lack of support for Mariadb CHECK constraint

[expired user #10759]'s profile image [expired user #10759] posted 7 years ago in General Permalink

Since 10.2 Mariadb supports field constraints which are not recognized by HeidiSQL. For example a table as follows:

CREATE TABLE test2 ( extra_info blob DEFAULT NULL CHECK (extra_info is null or json_valid(extra_info)) ) ENGINE=InnoDB;

Is returned as follows by the CREATE code tab:

CREATE TABLE test2 ( extra_info BLOB NULL DEFAULT NULL ) COLLATE='latin1_swedish_ci' ENGINE=InnoDB ;

Constraints on the field still work, but if I change a field or alter a table the field constraint vanishes which is really bad. I also cannot add a CHECK using HeidiSQL.

Please login to leave a reply, or register at first.