Hey Jonathan, When I was creating the Google AppEngine Cloud SQL driver I was having a very similar issue. The nature of the "cloud" is to not really hold open long-lived connections, it seems. I switched my driver code to FORCE SqlAlchemy's 'NullPool', which essentially does NO connection polling and requires a brand new connection each time.
I haven't tinkered with SQLSoup, but you might want to look where the SQLAlchemy connection is being established and set your pool class to NullPool. Not sure if that helps, but wanted to throw my two cents in! Cheers, Richie On Wednesday, 14 November 2012 12:45:02 UTC-7, JonathanQ wrote: > > Ok - it appears that the 2nd issue (DNS resolving) may be related to AWS: > https://forums.aws.amazon.com/thread.jspa?threadID=109414&tstart=0 > > But I am sure the first issue is something wrong with how we are using > SqlAlchemy/SqlSoup connections. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/OivpQEf8MnkJ. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
