[google-cloud-sql-discuss] Re: Row size too large + innodb_log_file_size flag

This feature to update the flag has already been initially reported on this issue tracker.

As a workaround, setting the 'innodb_strict_mode' to OFF often resolves the issue.  You can try the following instructions / explanation to add the table to your database:

Set innodb_log_file_size to 512MB

Set row_format to default/dynamic

Set innodb_strict_mode to OFF

How to add the table:
1.  Open your create_script.sql file with a text editor, and add one line above the "CREATE TABLE" line, the file should look like this afterwards:  

SET innodb_strict_mode = 0 ;

CREATE TABLE `history_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `coffee` longtext,
  .....

2.  Add the table to your database instance, replacing HOSTNAME with the hostname of the server, replacing DATABASE with the name of the database, and ensure that the path to the script is correct.

$ mysql -uroot -h HOSTNAME DATABASE < ~/path/to/create_script.sql

3.  Verify that the table has been created

If the above does not mitigate the issue, please open a new issue tracker and provide the redacted result of the following commands:

1. SHOW GLOBAL STATUS\G; 
2. SHOW VARIABLES\G; 
3. SHOW ENGINE INNODB STATUS\G; 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/c90328c0-d66a-4734-9067-d38afb121c28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.