Am I correct in assuming that you're using TurboGears 0.8? If you use a Transaction (in the SQLObject sense), you're implicitly not doing autoCommit. In 0.8, if you call hub.begin(), you should be working in a Transaction. In 0.9, transactions are implicitly created automatically for each request.
Kevin On 12/9/05, Mike Kent <[EMAIL PROTECTED]> wrote: > > I've gotten to the point in my project where I want to use > transactions. I'm using MySQL as my database backend. I understand > that for transactions I need to turn off autoCommit (and cache). > > Normally this is done by appending '?autoCommit=0' to the end of your > dburi string. However, the SQLObject interface to MySQL is broken in > regard to this. If you use this method, you will get a TypeError > exception, because the string '0' is not converted to an int where > needed. Using just '?autoCommit=' also does not work. There is a > ticket for this issue in the SQLObject bug tracking system. > > So, I need an alternate method of turning autoCommit off for my DB > connection, and I've not found it yet. Does anyone know how to do this? > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
