-
Bug
-
Resolution: Fixed
-
Highest
-
2.0
We use the TEXT datatype for large character fields, but this only holds a maximum of 64kb of data, or 65535 non-multibyte characters (when multibyte characters are used, this could be as little as 21845 characters).
MySQL accepts any string and silently truncates it when storing.
Solution is to move to larger datatypes such as MEDIUMTEXT (holds max 2^24 = 16,777,215 bytes) or LONGTEXT (2^32 = 4,294,967,295 or 4GB).
It's important to investigate the effects this may have on our full text comment search.
[CRUC-1824] MySQL silently truncates text fields to 64kb
Component/s | New: Server administration [ 50891 ] | |
Component/s | Original: Database [ 12766 ] |
Workflow | Original: FE-CRUC Bug Workflow [ 2941693 ] | New: JAC Bug Workflow v3 [ 2954051 ] |
Workflow | Original: FECRU Development Workflow - Triage - Restricted [ 1514770 ] | New: FE-CRUC Bug Workflow [ 2941693 ] |
Workflow | Original: FECRU Development Workflow - Triage [ 938860 ] | New: FECRU Development Workflow - Triage - Restricted [ 1514770 ] |
Workflow | Original: FECRU Development Workflow (Triage) [ 315393 ] | New: FECRU Development Workflow - Triage [ 938860 ] |
Workflow | Original: Simple review flow with triage [ 178520 ] | New: FECRU Development Workflow (Triage) [ 315393 ] |
Fix Version/s | New: 2.1 [ 14693 ] |
Labels | New: fecru_21_m1 |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Closed [ 6 ] |
Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |