If you haven't used app engine, I would try out the datastore through Google Big Tables first. It has limitations depending on your needs, but is designed to disallow common inefficiencies -- common mistakes in database design. I have found these much easier to use than SQLAlchemy, and the "limitations" actually pushed me to think of a much cleaner and better database/datastore design for my app.
I believe Google Cloud SQL is still experimental, and on the downside you will (I believe) have to pay for the service outright (whereas you can use Google Big Tables for free up to a certain point -- to test out and flesh out your app before deployment.) On Sat, Oct 8, 2011 at 1:04 PM, Iain Duncan <[email protected]>wrote: > Just saw the announcement that app engine now has an sql backend. Wondering > if anyone has got it working with Pyramid and SQLAlchemy yet? I've not yet > used AppEngine, but will check it out if I can get verification that this is > now possible. > > thanks! > Iain > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
