MySQL Bugs: #95143: No support for CHECK constraints in Workbench

Bug #95143	No support for CHECK constraints in Workbench
Submitted:	26 Apr 2019 6:30	Modified:	14 May 2019 7:32
Reporter:	Georgi Sotirov	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.16	OS:	Any
Assigned to:		CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

No CHECK constraint item for tables in navigator

Attachment: wb_8016_navigator_no_check.png (image/png, text), 22.59 KiB.

No way to create or modify CHECK constarints in table editor

Attachment: wb_8016_table_no_check.png (image/png, text), 86.89 KiB.

MySQL Workbench SQL Editor shows error on column check constraint

Attachment: wb_column_chk_error.png (image/png, text), 8.77 KiB.