Google cloud SQL Unstored procedures

[Serge Mac]

Hi

I am using Google cloud SQL and had faced with a problem. 

MySQL loses changes in stored procedures after a while.

The time at which loss occurs depends on the MySQL workload.

At the first time changes had been lost in about a month at low workload.

At high workload the changes are lost in about a 3-6 hours. 

This feature makes Google cloud SQL almost unusable.

Has anyone faced such a problem. Any suggestion or workarounds.

Thanks in advance

Serge

[Razvan Musaloiu-E.]

Can you make sure you issue a  FLUSH TABLES after making changes to stored procedures? MyISAM is not a transactional storage engine and data might be lost when mysqld is stopped and the data was not flushed. That might explain the behavior you are seeing. 

-- Razvan ME

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/4a669652-dd30-4d1c-b84f-f76a8377a0b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.