Bug #27239 | Relationship #chars and #bytes unclear for utf8 varchars | ||
---|---|---|---|
Submitted: | 17 Mar 2007 14:32 | Modified: | 16 Jun 2007 23:32 |
Reporter: | Roland Bouman | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | all | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | storage requirements, utf8, varchar |
[17 Mar 2007 14:32]
Roland Bouman
[17 Mar 2007 14:36]
Roland Bouman
I forgot to mention that this "The maximum size of a row in a MyISAM table is 65,534 bytes. Each BLOB and TEXT column accounts for only five to nine bytes toward this size." seems to imply this limitation is only in effect for MyISAM tables. however, I'm equally unable to create InnoDB, ARCHIVE, CSV, MEMORY, BLACKHOLE etc tables: "create table t_char( t varchar(21845) character set utf8) engine= archive; ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs " "create table t_char( t varchar(21845) character set utf8) engine= innodb; ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs"
[17 Mar 2007 19:58]
Valeriy Kravchuk
Thank you for a reasonable documentation request.
[16 Jun 2007 23:32]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.