Answers.Body: <p>I came into a similar problem with rich text areas and front end form submissions maxing out memory very easily. It may not solve your issue at the root but as you asked for any thoughts ideas or hacks and for the issue you state. In the rich text field options at the bottom you can change "column type" to "medium editor" which bumps storage from 64K to 4GB. 
  <a href="https://i.sstatic.net/YGMXV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/YGMXV.png" alt="enter image description here"></a></p>
  
  <p>Hope that helps in any slight way, sorry if it's off point. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-02T16:14:48.640Z
Answers.Text: Setting Max Lengths on your Plain Text fields will also affect their content column sizes.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-02T16:43:15.200Z
Answers.Text: Is there a standard set if no max length is given?
Answers.UserDisplayName: George Dunning
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-02T17:22:35.563Z
Answers.Text: By default it will be TEXT. If you set a Max Length it will be the smallest textual column type possible that can accommodate the Max Length.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-02T19:42:48.787Z
Answers.Text: Thanks @GeorgeDunning for the thought.  The innodb_file_format being set to barracuda has solved that previous issue (where this concept would have also helped), but as Brandon pointed out, setting a max length will affect the column size and actually increases the byte count.  At this point I have no choice but to install another instance of Craft.  Fortunately this new app is not quite as coupled to the others but may have to think about this for future updates.  Thanks for the thoughts and feedback!
Answers.UserDisplayName: jooosh
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-02T15:33:28.187Z
Answers.LastActivityDate: 2015-10-02T15:33:28.187Z
Answers.UserDisplayName: George Dunning
Body: <p>We are building out web applications for one client and have been using Craft to do so. However, I think we may have just hit a limit in the number of fields that Craft will support. More specifically this looks to be more of a MySQL limit. I had <a href="https://craftcms.stackexchange.com/questions/11480/internal-server-error-sqlstate42000-1118-row-size-too-large">recently encountered a similar issue</a> with a single entry that exceeded the row size with too much rich text. This was resolved with an update to the innodb file format, setting it to barracuda.</p>
  
  <p>Unfortunately this is not helping me in this instance as the limitation is now the total byte count for the number of columns, not the actual content.</p>
  
  <p>I've tried changing any columns in the table to 'text' and looked at any other tweaks based on <a href="https://dev.mysql.com/doc/refman/5.7/en/column-count-limit.html" rel="nofollow noreferrer">the described limitations</a>, but to no avail.</p>
  
  <p>I'm at a loss for what to do at this point as I am unable to even add one more field without an error being thrown and the DB becoming corrupt.</p>
  
  <p>As soon as I save that one more variable, I get this error:</p>
  
  <pre><code>Internal Server Error
  
  CDbCommand failed to execute the SQL statement:
  SQLSTATE[42000]: Syntax error or access violation:
  1118 Row size too large (&gt; 8126). Changing some columns to TEXT or BLOB may help.
  In current row format, BLOB prefix of 0 bytes is stored inline.
  </code></pre>
  
  <p>Then when I try to access the admin or any template on the site, I get this error:</p>
  
  <pre><code>Internal Server Error
  
  CDbCommand failed to execute the SQL statement: SQLSTATE[42S22]:
  Column not found: 1054 Unknown column 'content.field_heroCtaTitle' in 'field list'
  </code></pre>
  
  <p>The bummer with this error is I can only recover with a database restore. Didn't want to try and hack out the bad field.</p>
  
  <p>In the short term, I may try to replace some standard fields with matrix fields which should reduce the number of columns in the craft_content table, but this is not really an ideal approach.</p>
  
  <p>Any other thoughts, ideas, hacks would be greatly appreciated!</p>
  
Tags: <mysql>
Title: Bumping into max row size of 65k craft_content table in MySQL 5.5
ThreadText: # Bumping into max row size of 65k craft_content table in MySQL 5.5
  
  (Asked by: username_0 on 2015-10-02)
  
  We are building out web applications for one client and have been using Craft to do so. However, I think we may have just hit a limit in the number of fields that Craft will support. More specifically this looks to be more of a MySQL limit. I had [recently encountered a similar issue](https://craftcms.stackexchange.com/questions/11480/internal-server-error-sqlstate42000-1118-row-size-too-large) with a single entry that exceeded the row size with too much rich text. This was resolved with an update to the innodb file format, setting it to barracuda.
  
  Unfortunately this is not helping me in this instance as the limitation is now the total byte count for the number of columns, not the actual content.
  
  I've tried changing any columns in the table to 'text' and looked at any other tweaks based on [the described limitations](https://dev.mysql.com/doc/refman/5.7/en/column-count-limit.html), but to no avail.
  
  I'm at a loss for what to do at this point as I am unable to even add one more field without an error being thrown and the DB becoming corrupt.
  
  As soon as I save that one more variable, I get this error:
  
  ```
  Internal Server Error
  
  CDbCommand failed to execute the SQL statement:
  SQLSTATE[42000]: Syntax error or access violation:
  1118 Row size too large (> 8126). Changing some columns to TEXT or BLOB may help.
  In current row format, BLOB prefix of 0 bytes is stored inline.
  
  ```
  
  Then when I try to access the admin or any template on the site, I get this error:
  
  ```
  Internal Server Error
  
  CDbCommand failed to execute the SQL statement: SQLSTATE[42S22]:
  Column not found: 1054 Unknown column 'content.field_heroCtaTitle' in 'field list'
  
  ```
  
  The bummer with this error is I can only recover with a database restore. Didn't want to try and hack out the bad field.
  
  In the short term, I may try to replace some standard fields with matrix fields which should reduce the number of columns in the craft\_content table, but this is not really an ideal approach.
  
  Any other thoughts, ideas, hacks would be greatly appreciated!
  
  **Tags:** mysql
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-02. Score: 1
  
  I came into a similar problem with rich text areas and front end form submissions maxing out memory very easily. It may not solve your issue at the root but as you asked for any thoughts ideas or hacks and for the issue you state. In the rich text field options at the bottom you can change "column type" to "medium editor" which bumps storage from 64K to 4GB.
  [![enter image description here](https://i.sstatic.net/YGMXV.png)](https://i.sstatic.net/YGMXV.png)
  
  Hope that helps in any slight way, sorry if it's off point.
  
  > **Comments:**
  > **username_2**: Setting Max Lengths on your Plain Text fields will also affect their content column sizes.  
  > **username_1**: Is there a standard set if no max length is given?  
  > **username_2**: By default it will be TEXT. If you set a Max Length it will be the smallest textual column type possible that can accommodate the Max Length.  
  > **username_0**: Thanks @username_1 for the thought.  The innodb_file_format being set to barracuda has solved that previous issue (where this concept would have also helped), but as username_2 pointed out, setting a max length will affect the column size and actually increases the byte count.  At this point I have no choice but to install another instance of Craft.  Fortunately this new app is not quite as coupled to the others but may have to think about this for future updates.  Thanks for the thoughts and feedback!  
  
  ---
  
  