Bug #22759 | check constraint: missing feature and documentation | ||
---|---|---|---|
Submitted: | 27 Sep 2006 19:25 | Modified: | 6 Nov 2009 16:49 |
Reporter: | Maciej Pilichowski | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S4 (Feature request) |
Version: | 5.0.24a | OS: | Linux (opensuse 10.0) |
Assigned to: | CPU Architecture: | Any |
[27 Sep 2006 19:25]
Maciej Pilichowski
[29 Sep 2006 15:08]
Valeriy Kravchuk
Thank you for a reasonable feature request.
[20 Jun 2007 6:27]
vamsi mandava
is there any work around to fix this bug temperorily or we have to hanle the check in the front end before actually we are going to save the data
[18 Jul 2009 18:11]
Karsten Wutzke
This is true for every OS. Even in mid 2009 there's still no CHECK constraint. Come on!
[6 Nov 2009 16:49]
Valeriy Kravchuk
Duplicate of Bug #3464 actually.
[23 Jan 2019 16:28]
Paul DuBois
Posted by developer: Fixed in 8.0.16. Previously, MySQL permitted a limited form of CHECK constraint syntax, but parsed and ignored it. MySQL now implements the core features of table and column CHECK constraints, for all storage engines. Constraints are defined using CREATE TABLE and ALTER TABLE statements.