STILL.... Can't copy table to GCP MySQL

One would think, having had this database integration for how many year now, errors like this wouldn’t be something that the non-technical user would need to see; especially given the state of technology these days, one would expect this to be taken care of internally with a retry.

Error while copying table to DATABASE: {“method”:“POST”,“url”:“/api/template/copyAppTable”,“source”:{“src”:“fetch”,“response”:{},“text”:“{"title":"An error occured: ExceptionHandlerFramework.CustomerFacingException","status":400,"detail":"Row+size+too+large.+The+maximum+row+size+for+the+used+table+type%2c+not+counting+BLOBs%2c+is+65535.+This+includes+storage+overhead%2c+check+the+manual.+You+have+to+change+some+columns+to+TEXT+or+BLOBs","traceId":""}”},“status”:400,“statusText”:“”,“responseText”:“{"title":"An error occured: ExceptionHandlerFramework.CustomerFacingException","status":400,"detail":"Row+size+too+large.+The+maximum+row+size+for+the+used+table+type%2c+not+counting+BLOBs%2c+is+65535.+This+includes+storage+overhead%2c+check+the+manual.+You+have+to+change+some+columns+to+TEXT+or+BLOBs","traceId":""}”,“name”:“u”}

What’s crazy… there’s nothing on that table even remotely that size.

  • Largest cell size: 651 characters

¯\_(ツ)_/¯

5 Likes

Hi @MultiTech This isn’t about actual data size but MySQL row structure limits - the 65,535-byte limit applies to the total defined column sizes (e.g., many VARCHAR(255) columns), not current cell content, so you need to reduce VARCHAR lengths or convert some columns to TEXT/BLOB before copying to Cloud SQL.

1 Like