google-cloud-sql

问题 I have seen some questions about using SQLAlchemy on App Engine to connect to Google Cloud SQL. But I'm not sure if it is possible to develop using a local MySQL database and the existing SQLAlchemy dialect. On my first attempt, I added SQLAlchemy 0.8.0 to the app and defined a schema: from sqlalchemy import create_engine, Column, Integer, Table from sqlalchemy.ext.declarative import declarative_base Base = declarative_base() foo_table = Table('foo', Base.metadata, Column('id', Integer,

问题 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

问题 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? 回答1: There's now Google Cloud Trace for JDBC for exactly this use case. Google Cloud

问题 I tried to connect AppMaker to an existing Google SQL database without success. In Google Cloud, I created a second generation instance (europe-west1) and allow every IP (for the test). Next, I created a user, connected Workbench with the database and created a schema. Without problems. In AppMaker I use the following address to connect to the database: [domainName:]myprojectID:regionName:myinstanceID/mydatabase (with and without domain) Feedback: Unable to connect to Google Cloud SQL

问题 is it possible to access Google Cloud SQL from Google Compute Engine using the private network? It appears that Google Cloud SQL sees the public network IP for the Google Compute Engine instance. And, the web console doesn't allow entering the instance private address. 回答1: No it is not possible to access Google Cloud SQL instances via a private IP address. This this page confirms this, it says Note: You must use the external (public) IP address of the GCE instance ...when configuring

问题 I am following the Django sample for GAE and have problem to connect to Cloud SQL instance by Proxy from Google Cloud Shell. Possibly related to permission setting since I see the request not authorized, Other context, "gcloud beta sql connect auth-instance --user=root" has no problem to connect. I have a service account for SQL Proxy Client. I possibly miss something. Could someone please shed some light? Thanks in advance. Thanks in advance. Proxy log: ./cloud_sql_proxy -instances=auth

问题 I recently upgraded a Postgres 9.6 instance to 11.1 on Google Cloud SQL. Since then I've begun to notice a large number of the following error across multiple queries: org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.78044234" to 2097152 bytes: No space left on device From what I've read, this is probably due to changes that came in PG10, and the typical solution involves increasing the instance's shared memory. To my knowledge this isn't possible

问题 I have been looking at the console’s billing as far as Cloud SQL and the VM Instance is concerned. I see that a lot of the cost comes from the idling hours of the Cloud SQL IP address. I am unsure as to where the settings are for this as i have tried to “unassign” the ip address that is associated with my Cloud SQL Instance. Are these charges static, as in am I always, no matter what, going to be charged for the ip address constantly or is there a way to turn this off when I am not using the

问题 I recently started getting the error "Unexpected exception upon serializing continuation" on a spreadsheet Google Apps Script when trying to debug. The error seem to start after I created a connection to the Google CloudSQL api. This error still occurs even after commenting out the jdbc object constructor. It appears that others have had this issue and needed a Google Tech to resolve the issue. I have searched all of the discussion boards for a solution to this issue with no luck. Any chance

问题 I know AppEngine application runs in a restricted "sandbox" environment so that it can access limited resources like request execution time limit 60 sec (which is for speed optimization purpose) read from external file but can not write ,etc AppEngine provides a good high replication Datastore ,which is so good to store data but it is hard to mange number of quires to perform simple operation like insert, update, delete and update as it uses NoSql(basically jpa and jdo). Because of this we