Hacker News Reader

Comment by grouseway | Hacker News Reader

What is the access to your hosted postgres like? Do you still have to use that proxy thing? I'm wondering how much effort is require to move a sqlalchemy based app over to this.

View on HN

You would use Cloud SQL to access PostgreSQL.

Here's how you configure your App Engine standard environment project to use Cloud SQL: https://cloud.google.com/appengine/docs/standard/python3/usi...

The Cloud SQL for PostgreSQL docs contain code samples to get you started: https://cloud.google.com/sql/docs/postgres/

This should all work with SQLAlchemy.

It is not possible to access Postgres based CloudSQL from Python on AppEngine standard. See here:

https://cloud.google.com/sql/docs/postgres/connect-app-engin...

Note that only node and Java are listed under non-Flex.

I got burned by this and had to start over with MySQL.

> It is not possible to access Postgres based CloudSQL from Python on AppEngine standard.

It is possible on the new (beta) Python 3. 7 runtime on AppEngine standard:

https://cloud.google.com/appengine/docs/standard/python3/usi...

Then they should update their docs.

Thanks for noticing this. We'll get this updated.

If you're an existing AppEngine standard user/customer, it's pretty likely that that means you will not be able to take advantage of PostgreSQL, as the new runtime does NOT give you access to a ton of their existing services that you are probably already using (such as datastore.)

Hi optimusclimb -- just want to make clear that using Cloud SQL to connect to PostgreSQL should work using Python 3.7 on the App Engine standard environment. Your earlier comment accurately pointed out a gap in our docs. We're going to address that -- thank you.

If you try Cloud SQL and find that it doesn't work with PostgreSQL on this new runtime, that's a bug and we need to fix it.

I think what he's saying is you're currently using Python 2.7 on Standard and using existing built-in services like task queue, memcache, ndb, etc then switching to the new Python 3.7 runtime (to be able to connect to Postgres) runtime really isn't possible since there aren't non-rewrite solutions for those missing pieces.

Reply on news.ycombinator.com