Oh... I'll give it a try... I'm using some parts of z3c.saconfig without knowing too well what they do... I took this tutorial: http://grok.zope.org/documentation/how-to/orm-using-megrok.rdb-and-sqlalchemy
... and I didn't look much further. I'll try to dig into the packages you mentioned. Looks like they might be helpful Thanks! 2011/3/24 Wichert Akkerman <[email protected]>: > On 3/23/11 23:11 , Hector Blanco wrote: >> >> Yeah... the closing thing is because this is going to be in a >> webserver, and the framework that controls the requests really, really >> messed up everything (mysql daemon, sqlalchemy...) if the http request >> was canceled (If I had a user pressing F5 in Firefox all the time, I >> got coredumps that stopped the server) >> >> That was me: >> http://groups.google.com/group/sqlalchemy/browse_thread/thread/5a3c7c8056cf6a60/6805bbe38667b9be?lnk=gst&q=Hector+Blanco#6805bbe38667b9be >> >> That's why I decided to commit, close, and such as soon as possible >> (leave the sessions opened as little as possible) >> >> The problem seems to have improved lately (there was an update of the >> Zope framework recently, and the problem seems to have "relaxed" a >> bit)... but I'm still scared!! According to some other documents/posts >> I've read, maybe a commit (without the closing) would still work, >> though. > > FWIW I do a fair bit of SQLAlchemy things in Zope and have never seen such > problems, nor have I ever heard of anyone seeing problems like that using > Zope and SQL, which is a fairly common setup. Perhaps the missing trick here > is to use zope.sqlalchemy and/or z3c.saconfig to > handle the SQLAlchemy/Zope integration. > > Wichert. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
