Bug #82913 | manual should clarify storage requirements for variable length character sets | ||
---|---|---|---|
Submitted: | 8 Sep 2016 21:49 | Modified: | 18 Oct 2016 17:55 |
Reporter: | Morgan Tocker | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.7 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[8 Sep 2016 21:49]
Morgan Tocker
[8 Sep 2016 22:46]
MySQL Verification Team
Thank you for the bug report.
[18 Oct 2016 17:55]
Daniel Price
Posted by developer: The reference section was updated with the following information: http://dev.mysql.com/doc/refman/5.7/en/char.html "For InnoDB COMPACT, DYNAMIC, and COMPRESSED row formats, CHAR is treated as variable-length type if the length of the column value is greater than or equal to 768 bytes, which can occur if the maximum byte length of the character set is greater than 3, as it is with utf8mb4, for example. When treated as a variable-length type, a CHAR column value may be chosen for off-page storage." Updates were also made to: http://dev.mysql.com/doc/refman/5.7/en/innodb-physical-record.html http://dev.mysql.com/doc/refman/5.7/en/innodb-row-format-dynamic.html http://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html Updates were made to all versions of the reference manual (5.5,5.6,5.7,8.0). Thank you for the bug report.