This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Marko.Kohtala
Recipients Marko.Kohtala
Date 2010-05-28.11:24:05
SpamBayes Score 0.00011186716
Marked as misclassified No
Message-id <1275045847.96.0.603082208201.issue8842@psf.upfronthosting.co.za>
In-reply-to
Content
The Windows builds seem to come with SQLite library version 3.5.9, as seen from sqlite3.sqlite_version. This is from 2008-May-12.

I've been using the sqlite3 module, but keep running into bugs on Windows. Replacing the DLLs\sqlite3.dll with a newer library (sqlite is going at version 3.6.23), seems to fix those problems.

One problem was locking failures when performing a lot of changes and committing after each change. This happens within a single script accessing the file, apparently locking himself out. I did not want users needing to patch installed Python, so I got around that by removing the smaller commits and making one huge commit at end.

Now I had a problem that ANALYZE does not result in good queries. Performing ANALYZE with newer library speeded queries significantly. I do not know how to get around that.

On Linux I see Python 2.6 using sqlite 3.6.x versions, so I'd expect the reason for old library on Windows can not be incompatibility.
History
Date User Action Args
2010-05-28 11:24:08Marko.Kohtalasetrecipients: + Marko.Kohtala
2010-05-28 11:24:07Marko.Kohtalasetmessageid: <1275045847.96.0.603082208201.issue8842@psf.upfronthosting.co.za>
2010-05-28 11:24:06Marko.Kohtalalinkissue8842 messages
2010-05-28 11:24:05Marko.Kohtalacreate