Hello Brian,
If you filter your imported data in any way, CloudSQL or MySQL in general will see this as a legitimate operation, that does not justify any special logging the way errors or bugs would require. Have you examined all logging levels, as selected by using the drop-down menu offered in the developers' console, specifically on the logging screen? I mean navigating to logging → log level (default "Any log level"), and choosing from critical, error, warning, info, debug, offered by the drop-down menu.
If you want to follow all database operations in detail on pure MySQL, you need to turn on the general log. This action would require SUPER privileges for Cloud SQL, a feature that was turned off a while ago, as recorded in this announcement. It is therefore not possible to use the general log, as this solution is unsupported in CloudSQL.
You may get more detail on importing data in CloudSQL from the "Overview of Importing and Exporting Data" documentation page.
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/2a83155e-2910-4124-9a0e-7474bc0cc770%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment