On Aug 12, 2010, at 3:16 , Guyren G Howe wrote: > It appears that the problem may relate to the way some middleware I inherited > is setting up the session. > > It's set to autocommit=false, autoflush=true. > > However: the problem I now see is that a transaction starts when I execute > this line: > > website = session.query(WebSite).filter_by(domain=search).one() > > I hadn't even thought to check this. Why on earth would this need to start a > transaction?
Confirming this. Going through and adding a session.commit() at the end of every function where I execute queries fixes the issue. This *appears* to be madness. I can't imagine why one would want a mode of access to a database wherein queries are always run in a transaction. But I'm certainly willing to be convinced otherwise. :-) -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
