Search code examples
mysqleventsstored-proceduresrollbackgoogle-cloud-sql

MySQL SPs and Events being automatically rolled-back by Google Cloud SQL

I have migrated my production MySQL schema to Google Cloud SQL. Various modifications have been necessitated to existing Stored Procedures & Scheduled Events, and some new ones deployed. HOWEVER, I have been noticing that where I leave everything working at 6PM, by the time I arrive back at my desk next morning, many (all?) SP & Event alterations are rolled back to some earlier state to development, and all my routines are failing or going crazy. The Data itself does not appear to be affected or rolled back, and continuous new inserts are succeeding. I'm thinking that the automatic Backup / replication might be overwriting my SP & events. Anyone know how to control this? Thanks, -Paul

Solution

  • Please issue a FLUSH TABLES after making changes to the stored procedures. That should decrease the chances of MyISAM tables not persisting a server restart.