[google-appengine] Re: Google Cloud SQL Incident #18002

In addition, this documentation shows you how to view your Cloud SQL instance information [1] [1] https://cloud.google.com/sql/docs/mysql/instance-info -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and st

[google-appengine] Re: Google Cloud SQL Incident #18002

You can view your Cloud SQL MySQL/PostgreSQL version through the Google Cloud Console: from the "Navigation" Menu --> select "SQL" --> click on the "Instance ID" --> Select the "Overview" tab --> scroll down to the "Properties" section --> view "Database version" I hope this is clear. -- You

[google-appengine] Re: Google Cloud SQL Incident #18002

Thanks Katayoon, I have created a new ticket. But there is no instance... This is strange. The console says: This version has no instances deployed. Where can I check which Cloud SQL version we are using? On Friday, August 24, 2018 at 1:17:26 AM UTC+3, Katayoon (Cloud Platform Support) wrote:

[google-appengine] Re: Google Cloud SQL Incident #18002

The incident you mentioned was related to the Cloud SQL v1 instance availability in us-central1-a. If you have such an instance and you are still encountering issues related to this instance, I recommend that you open a PRIVATE case in the Issue Tracker

[google-appengine] Re: Google Cloud SQL Incident #18002

It is not up and running. There are still problems. And the logs does not tell anything meaningful. Just this: The request failed because the instance could not start successfully Why the instance is not starting successfully? Can I solve this issue somehow? Or to create new application on anoth

[google-appengine] Re: Google Cloud SQL Incident #18002

Your site is up-and-running once again. The issue has been addressed meanwhile: *"The issue with Cloud SQL First Generation instance unavailability has been resolved for all affected projects as of Thursday, 2018-08-16 10:38 US/Pacific.

[google-appengine] Re: Google Cloud SQL: Can't add authorized application

This unfortunately is a known issue. Feel free to star the issue here for visibility. On Sunday, January 10, 2016 at 1:42:07 AM UTC-5, Zack Hine wrote: > > Just want to add, that I've also tried installing the Google Cloud SDK and

[google-appengine] Re: Google Cloud SQL: Can't add authorized application

hi Zack. I'm trying to contact you over Hangouts to get the project Id and have a look. Please accept the invite. Thanks. On Sunday, 10 January 2016 07:42:07 UTC+1, Zack Hine wrote: > > Just want to add, that I've also tried installing the Google Cloud SDK and > running: > gcloud sql instances

[google-appengine] Re: Google Cloud SQL: Can't add authorized application

Just want to add, that I've also tried installing the Google Cloud SDK and running: gcloud sql instances patch my-instance --authorized-gae-apps my-app And the result is: The following message will be used for the patch API method. {"project": "my-app", "instance": "my-instance", "settings": {"a

[google-appengine] Re: Google Cloud SQL

Could you elaborate how you get to the "SQL Prompts" exactly? On Sunday, March 29, 2015 at 2:35:25 PM UTC-7, Thomas Boyce wrote: > > I just have a general query/problem. > > I have a Google App Engine PHP/MySQL website. The website works fine and > the database works correctly. I have connected t

[google-appengine] Re: google cloud sql server error

I solved but Thanks I was an authorization ID misspell. On 2월16일, 오전1시36분, Robert Kluin wrote: > Hi Mansik, > Check your app's log in the log viewer on the appspot dashboard. > The error should be detailed there. > > Robert > > > > > > > > On Wed, Feb 15, 2012 at 12:44, Mansik Kim wrote: > > W

Re: [google-appengine] Re: Google Cloud SQL

Thanks Robert and Brandon! I was really concerned that making Cloud SQL available would cause people to try to fit everything into a SQL peg instead of trying to think what the best persistence model is. SQL is really good for some things, but so is the datastore. I think the true sweet spot for a

[google-appengine] Re: Google Cloud SQL

I agree. GQL is superior from a performance perspective. You can understand what is going on under the hoord. Switching from SQL to GQL you have to rethink your model : denormalizing it. The benifits (performance and scaleability) are great and it feels good too. At the end working with GQL is