Right, we understood that. However *before* adding the brokenCursorAPIs setting, you reported an issue with local MySQL, and that report doesn't make sense.
If you have the time, we'd appreciate it if you could revert the brokenCursorAPIs setting and show the server log for a failed attempt to contact local MySQL. We just want to double-check that this is in fact a Google-CloudSQL-specific problem.
If you have the time, we'd appreciate it if you could revert the brokenCursorAPIs setting and show the server log for a failed attempt to contact local MySQL. We just want to double-check that this is in fact a Google-CloudSQL-specific problem.
Comment