> It occurred to me that the COMMIT log message would actually come from > SQLObject anyhow, so the sqlite version shouldn't make a difference. > Here's a few more things to look at: > > In [2]:hub.uri > Out[2]:'sqlite:///tmp/book.db?debug=1' > > In [3]:hub.supports_transactions > Out[3]:True > > In [7]:Bookmarks.select().count() > (some output) > > In [8]:hub.threadingLocal.connection > Out[8]:<sqlobject.dbconnection.Transaction object at 0x111f290> > > Assuming those things all match up, commit *should* work. If one of > those things doesn't match up, commit won't do anything (which is what > you're seeing). > > Kevin I tried it, and all four of those tests work as expected, but hub.commit still didn't do anything.
I saw that there's a new version of pysqlite out at the cheeseshop, so I updated from pysqlite 2.1.1 to 2.1.2 and now I get hub.threadingLocal.connection AttributeError: thread._local object has no attribute 'connection' And now my inserts happen imediately, and I don't have to use database.commit_all() Things are crazy here with another project, so I am only debugging a bit here and there, which makes this all a lot harder. ;) -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog
