I looked quite a bit and could not find a workaround to skip these errors in Cloud SQL. Unfortunately, these errors have to be addressed in the initial DB. Another option is to use MySQL on a Compute Engine instance as mentioned in this thread [1].
I also suggest posting this issue on StackOverflow but with MySQL tags, to see if anyone in the community has any other suggestions.
[1] https://issuetracker.google.com/issues/128603238#comment4
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/f06985eb-3f80-4d94-b9ee-6ad8c39519fa%40googlegroups.com.
No comments:
Post a Comment