由Google Cloud SQL自动回滚的MySQL SP和事件 [英] MySQL SPs and Events being automatically rolled-back by Google Cloud SQL

问题描述

我已将我的生产MySQL模式迁移到Google Cloud SQL。现有的存储过程&计划事件和部署新的事件。
然而，我一直在注意到，我下午六点钟下班的工作，当我第二天早上回到办公桌前，很多（全部）SP&事件改变回到一些早期的状态来发展，我所有的例程都失败或者疯了。数据本身不会受到影响或回滚，连续的新插入成功。
我认为自动备份/复制可能会覆盖我的SP&事件。任何人知道如何控制这个？
谢谢，
-Paul

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

推荐答案

请发出一个 FLUSH TABLES 更改存储过程后。这应该会降低MyISAM表不会持续重新启动服务器的机会。

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.

这篇关于由Google Cloud SQL自动回滚的MySQL SP和事件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！