I got a response directly from google; but forgot to post the response here. Currently, the mysql logs are not exposed directly to the user. What was happening to me was that I had a view that referenced tables/fields no longer in the database (cleanup issue on my part); so the dump routine was failing but the exact mysql error message was not being passed all the way to the Google Cloud SQL console. Google responded very quickly and accurately. They also said they have plans to eventually expose the mysql logs to the admin.
I thought it most interesting part of this was the dump routine actually checked the validity of the statements (e.g. the create view statement) it was creating and not just blindly writing it out. Nice, because then you don't have to deal with it when you are importing it.
On Wednesday, August 21, 2013 5:27:40 AM UTC-10, Lee S. wrote:
-- I thought it most interesting part of this was the dump routine actually checked the validity of the statements (e.g. the create view statement) it was creating and not just blindly writing it out. Nice, because then you don't have to deal with it when you are importing it.
On Wednesday, August 21, 2013 5:27:40 AM UTC-10, Lee S. wrote:
Do you see anything in the operations log? Are you using http://cloud.google.com/console ? Also, what's the instance name??
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/64de959b-19ea-40f8-9553-c0790aa84733%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment