MySQL Forums
Forum List  »  InnoDB

Re: Jack WH-"Row size too large" error is triggering - when I don't think it should be
Posted by: Rick James
Date: August 22, 2016 03:53PM

It sounds like you should run away from ExpressionEngine .

That many columns in a table is 'bad design'.
TINYTEXT is sub-optimal; it should never be used.
utf8 should not be used for base64; ascii is sufficient.
INT(4) -- the 4 is meaningless; it implies the process generating it does not understand the datatype.

Barracuda + ROW_FORMAT=Dynamic is probably suitable for you.

You probably want to unpack the base64 into a BLOB? Consider loading into a MyISAM table, then splitting the data across multiple InnoDB tables as you cleanse the input.

What does the "field_id.../field_ft" pattern mean? Are these pairs of normalized data? It it a key-value store saved in a single row? (Shudder!) Are the keys actually numeric?

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Jack WH-"Row size too large" error is triggering - when I don't think it should be
433
August 22, 2016 03:53PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.