The Row size too large error is reported when the text field is updated.

When the text field is updated, the Row size too large error occurs. cause: the group buying development report says there is an error during the update. UPDATE the SQL statement www.2cto.com as follows: UPDATE table_name d SET d. column_name = 'aaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa 'where d. ID = 100976; Error Code: 1118Row size too large. The maximum row size for the used table type,
Not counting BLOBs, is 8126. You have to change some columns to TEXT or BLOBs: The updated field only involves the column_name field and is of the TEXT type. Www.2cto.com: The TEXT content exists in off-page under the Dynamic table format.
Calculates the row size. Barracuda corresponds to row_format (dynamic, compress ).
All the content of is the Antelope corresponding to row_format (compact, redundant) stored in off-page.
Yes, 786B is stored in row. More than one part has off-page, and the server configuration is innodb_file_format = Barracuda. It is reasonable to say that all tables use a dynamic structure. But! The reason is as follows: from the document: To preserve compatibility with those prior versions, tables created
The InnoDB Plugin use the prefix format, unless one of ROW_FORMAT
= DYNAMIC or ROW_FORMAT = COMPRESSED is specified (or implied)
On the create table command. That is to say, the specified row_format = dynamic is not displayed during TABLE creation, even if innodb_file
_ Format = row-format or compact of the Barracuda table. Therefore, if the text field of a table is many, we recommend that you add
Row_format = dynamic