Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Since there's no context where someone will want a JSON type without the constraint, and excluding it causes compatibility problems with MySQL, why not map
CREATE TABLE t (j JSON); |
to
CREATE TABLE t ( |
j JSON
|
CHECK (JSON_VALID(j)) |
);
|
Attachments
Issue Links
- relates to
-
MDEV-9144 JSON data type
- Closed
-
MDEV-13313 JSON type alias is insufficiently compatible
- Closed