* ALTER TABLE query, not UPDATE query! Anyways, I hope it would be clear from the context.
Feel free to update the thread if you find any other useful information that could help other users. Cheers! Nick Cloud Platform Community Support On Thursday, May 12, 2016 at 12:27:44 PM UTC-4, Nick (Cloud Platform Support) wrote: > > I'm glad to hear you were able to run the update query once the fields had > been modified. I was worried you'd be unable to shrink the fields. I expect > you'll see huge savings of efficiency and storage space by changing CHAR to > VARCHAR and generally shrinking the size of various fields. > > You might also want to consider further normalization of the table, > linking the primary key ID to rows in another table which stores some of > the columns which might not be necessary to retrieve on each query, > allowing JOIN queries to be run in the case that those columns are needed > as well. > > We look forward to logging the Feature Request you make - we're always > looking for suggestions from users as to what they believe would be the > most useful features to work on. > > Cheers, > > Nick > > > On Wednesday, May 11, 2016 at 8:08:34 PM UTC-4, channing dev wrote: >> >> Nick, >> >> At before I have 5 TEXT and so many char(255) and varchar(2000). Now I >> have changed to 2 TEXT and 3 MEDIUMTEXT, and change char(255) to >> varchar(255), change varchar(2000) to varchar(500), so it works fine. >> But the issue in InnoDB I think is exist, Google cloudsql should support >> innodb_file_format flag. >> OK, I will try to request a Public Issue Tracker to Google to make GAE >> more powerful. >> >> Thank you. >> >> 在 2016年5月12日星期四 UTC+8上午12:02:20，Nick (Cloud Platform Support)写道： >>> >>> Let me know how it goes, whatever you decide to do, and feel free to >>> post back here if you run into any troubles. I'm sure this thread could be >>> useful to future users. >>> >>> Cheers, >>> >>> Nick >>> Cloud Platform Community Support >>> >>> On Tuesday, May 10, 2016 at 8:19:47 PM UTC-4, channing dev wrote: >>>> >>>> Nick, >>>> >>>> I see. Now I will firstly change my table structure, it seems no other >>>> way as I know. >>>> >>>> Thank you. >>>> >>>> 在 2016年5月11日星期三 UTC+8上午4:48:24，Nick (Cloud Platform Support)写道： >>>>> >>>>> Cloud SQL only supports a subset of MySQL flags >>>>> <https://cloud.google.com/sql/docs/mysql-flags>, although you could >>>>> file a Feature Request in the Public Issue Tracker for Cloud SQL >>>>> <https://code.google.com/p/googlecloudsql/issues/list> to see >>>>> innodb_file_format >>>>> <https://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_file_format> >>>>> >>>>> supported. Are any of the other options from my last post possible to use? >>>>> >>>>> On Monday, May 9, 2016 at 8:18:14 PM UTC-4, channing dev wrote: >>>>>> >>>>>> Hi Nick, >>>>>> >>>>>> OK. I found some documents about this, found one way to solve it. >>>>>> That is I want to change InnoDB to Barracuda format. How to config this >>>>>> on >>>>>> Google Cloud SQL? There is no this tag on Cound SQL console. Or you have >>>>>> some other advice to me? >>>>>> >>>>>> Thanks. >>>>>> >>>>>> >>>>>> 在 2016年5月10日星期二 UTC+8上午1:55:17，Nick (Cloud Platform Support)写道： >>>>>>> >>>>>>> Hey Channing, >>>>>>> >>>>>>> This isn't a Cloud SQL restriction but rather an InnoDB restriction. >>>>>>> You can read about it in the links given in this Stack Overflow Q&A >>>>>>> from a user who saw the exact same error message >>>>>>> <http://stackoverflow.com/a/15585700/4270992>. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Nick >>>>>>> Cloud Platform Community Support >>>>>>> >>>>>>> On Monday, May 9, 2016 at 3:20:28 AM UTC-4, channing dev wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I have a GAE instance on Google cloudsql and created one database >>>>>>>> on it, in the database there is a table which have 40 fields, and have >>>>>>>> 5 >>>>>>>> text fields. >>>>>>>> The issue is when I run update sql to update one of the text field, >>>>>>>> cloudsql alert me with below error: >>>>>>>> [Err] 1118 - Row size too large (> 8126). Changing some columns to >>>>>>>> TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may >>>>>>>> help. >>>>>>>> In current row format, BLOB prefix of 768 bytes is stored inline. >>>>>>>> I can make sure the field is text and the update value is less than >>>>>>>> 64 kb, and in my another table which have 10 fields we can update >>>>>>>> successfully use the same sql. >>>>>>>> Does cloudsql have this issue when a table have more than some >>>>>>>> fields? e.g. more than 30? or 35? >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7cba3ced-e2b7-4f19-90ee-d2a5824cb435%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
