Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.7
-
None
Description
Now it maps to TEXT. It'd be more compatible to map it to
LONGTEXT CHARACTER SET utf8mb4 CHECK(JSON_VALID(col)) |
But auto-adding a constraint is questionable. An unexpected constraint in the table definition, performance implications, strange errors if one manually specifies some constraint for this column.
Attachments
Issue Links
- relates to
-
MDEV-9144 JSON data type
- Closed
-
MDEV-13916 Enforce check constraint on JSON type
- Closed