On Feb 15, 2008, at 11:14 AM, Michael Schlenker wrote:
Michael Bayer schrieb:
no idea. below is a revised version, where the main revision is that
theres no SQLAlchemy ;). So I think you should submit this to the
bug
tracker on www.sqlite.org.
Actually this is sorta interesting
I'm trying to track down whose code is responsible for this problem.
Your example (and I suppose sqlalchemy) use an sqlite3 module, which
seems to only exist within the python source tree. upgrading pysqlite
from initd.org gives me a pysqlite2 module. (Using the
pysqlite2.dbapi2 module does not
I think I understand the relationship between pysqlite2 and sqlite3
(the second being a stdlib snapshot of the first) and have found the
code in sqlalchemy that will use pysqlite2, if present, over sqlite3,
so having installed the latest version of pysqlite2, I should be fine.
Any idea why the
On Feb 15, 2008, at 3:23 PM, Jonathon Anderson wrote:
I think I understand the relationship between pysqlite2 and sqlite3
(the second being a stdlib snapshot of the first) and have found the
code in sqlalchemy that will use pysqlite2, if present, over sqlite3,
so having installed the
