uggh, pysqlite 2.1 fixed some other problems I was having in
transactions iirc. I'm scared to upgrade/downgrade :(
On 1/11/07, Michael Bayer [EMAIL PROTECTED] wrote:
the important thing is your sqlite version. im on 3.2.1. my
pysqlite seems to be2.0.2 ? maybe a new pysqlite bug, not
oh, nice. upgrading sqlite to 3.3.7 and rebuilding pysqlite2 fixed it
-- sorry for the noise.
On 1/12/07, Kumar McMillan [EMAIL PROTECTED] wrote:
uggh, pysqlite 2.1 fixed some other problems I was having in
transactions iirc. I'm scared to upgrade/downgrade :(
On 1/11/07, Michael Bayer
when i run this program, I get no errors.
a few things to note:
it makes no sense to do a session.flush() after youve dropped the
table (similarly, it makes no sense to flush() before youve done
anything but thats less of an issue). if there were any modified
state within your session
