Rowsiz1_large error when updating the text field _ MySQL

When the text field is updated, rowsiz1_large reports bitsCN.com

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

Cause:

Group buying Development report indicates an error occurred during the update.

Www.bitsCN.com

The update SQL statement is as follows:

UPDATE table_name d SET d. column_name = 'aaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'

WHERE d. ID = 100976;

The error message is as follows:

Error Code: 1118

Row 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

Doubt:

The update field only applies to the column_name field and is of the TEXT type.

Www.bitsCN.com

My personal understanding is:

The TEXT content exists in off-page in the Dynamic table format.
Calculates the row size.

Barracuda corresponds to row_format (dynamic, compress ).
All content is stored on off-page.

Antelope corresponds to row_format (compact, redundant ).
Yes, 786B is saved in row, and more than one part has off-page

The server configuration is innodb_file_format = Barracuda

All tables use a dynamic structure.

But! The reason is as follows:

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, when creating a table, the specified row_format = dynamic is not displayed, even if innodb_file
_ Format = row-format or compact of the Barracuda table

Therefore, we recommend that you add
Row_format = dynamic

BitsCN.com