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 /

I am trying to optimise performance in an app-engine Java app using cloud sql gen2. It would help a lot if I could trace calls to cloud sql just like I can trace RPC calls to the datastore in the stackdriver trace details. Is this somehow possible, or maybe planned? Or is the only alternative to do log.info() calls with milliseconds? Or is there some other way to add event markers for tracing / profiling? There's now Google Cloud Trace for JDBC for exactly this use case. Google Cloud Trace for JDBC is a custom JDBC driver which intercepts calls to the actual JDBC driver (e.g. Cloud SQL's) and

We are having a Google App Maker app using Google Cloud SQL tables. Our location is Prague, Central Europe and saving one record takes incredible 240ms at minimum. It looks like Google App Maker has a proxy just close to my location (latency ~20ms). However our instance set up in US-Central1 (which is recommened by Google to provide Google App Maker apps with the best performance) shows ~120ms ping. We have tried many things including changing the instance location to Frankfurt, Germany (~25 ms). In this case, it took even longer (500ms per record). Our queries seemed to be round-tripping this

I just started getting this Error today while using MySQL workbench, and noticed it showing up in my application as far back as saturday. Anyone else getting it? Have any idea what might be causing it? ERROR Error Code: 1290. The MySQL server is running with the --read-only option so it cannot execute this statement Running just a simple insert generates the error. Eg.. INSERT INTO Job1111 . SubsWeld ( fk_SubmissionId , WeldSpool1 , WeldSpool2 , WeldDrawingNumber , WeldLineNumber , WeldSheetNumber , WeldTimeInForm , WeldLineSpec , WeldNumber , WeldStencil , WeldSize , WeldThickness , WeldType

I have an App Engine application which uses Google Cloud SQL, and from a page in my application I am doing some database operation; whenever this page is accessed, it is not able to perform all database operations. When I go to the console, all I see is /_ah/queue/__deferred__ . I am able to run the application without any issues on localhost so code has no errors, however, there is an issue with the Cloud SQL after deploying it. Note : I have not used queues anywhere in my code. What is the actual cause for /_ah/queue/__deferred__ to appear in App Engine logs? I had a similar issue. I've

I'm trying to populate a mysql db with a csv that i have in cloud storage I'm using the API Explorer to execute the request with the following request body: { "importContext": { "csvImportOptions": { "columns": [ "col1", "col2", "col3" ], "table": "table_name" }, "database": "db_name", "fileType": "CSV", "kind": "sql#importContext", "uri": "gs://some_bucket/somecsv.csv" } } When i hit the execute button i receive a 200 response with the following body { "kind": "sql#operation", "selfLink": "https://www.googleapis.com/sql/v1beta4/projects/somelink", "targetProject": "some-project", "targetId":

I'm trying to install WordPress on Google's App Engine for PHP with Cloud SQL. However, I can't give my WP database user access to their DB. Looking at the users in my Cloud SQL instance, the grant privilege for the root@% account is unchecked. However, in their WP setup doc, they say to use GRANT ALL for the new database user. See step 6 at: https://developers.google.com/appengine/articles/wordpress Subsequently, I cannot give rights to the new WordPress DB to the user account for the app. Anyone know what they expect us to use? Turns out that you have to go through a few steps in the cloud

I have some data in Google Cloud SQL, which I am trying to transfer to Google Cloud Storage using Cloud SQL API(beta) (export) function. For this, I have installed jupyter notebook on google compute engine and I am running the python code (to connect to cloud sql API and export the date to cloud storage in a csv file) on that. The python code does not throw any error and also there is no error body in API response. However, the API's response says " u'status': u'PENDING' " and I see the following error (in logs of Cloud SQL Dashboard) : error uploading CSV file to GCS: gs://[BUCKET_NAME]/[FILE