> Date: Wed, 24 Dec 2014 14:53:47 +0000 > From: Simon Slavin <slav...@bigfraud.org>
> Sorry, I may have just realised what's wrong. You are misusing your > python library. > See the documentation at > > <https://docs.python.org/2/library/sqlite3.html> > > You cannot always use .execute against the connection to the > database. You need to create a Cursor to the connection first, > and use .execute against that as documented in 11.13.3. Your code > works fine here I actually tried this same idea yesterday, but it made no difference. Even manually creating cursors and executing all statements through them yielded the exact same problem. For simplicity, I kept the code sample short, but I've tried dozens of different ideas over the last two days to get to the bottom of this. I even spent time studying the _sqlite.c code base https://svn.python.org/projects/python/trunk/Modules/_sqlite/ to see if I could track the source of the problem -- but I'm coming up blank. I was getting hung up with trying to understand whether or not the concept being attempted was valid sqlite. The comments I hearing is that from the sqlite perspective, the concept SHOULD work, but that there may in fact be some sort of bug/feature in the pysqlite connector code? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
