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
-
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Description |
Now it maps to {{TEXT}}. It'd be more compatible to map it to
{code:sql} LONGTEXT CHARACTER SET utf8mb4 CHECK(JSON_VALID(col)) {code} |
Now it maps to {{TEXT}}. It'd be more compatible to map it to
{code:sql} LONGTEXT CHARACTER SET utf8mb4 CHECK(JSON_VALID(col)) {code} 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. |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Fix Version/s | 10.2.8 [ 22544 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 81658 ] | MariaDB v4 [ 152478 ] |