Re: pysqlite design decisions
Roger Binns <[email protected]>
| Newsgroups | gmane.comp.python.db.pysqlite.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gerhard Häring wrote: | Did you mean SQLite version or pysqlite version? Definitely the former, and the latter can only have bug fixes - nothing that changes semantics. | As for which SQLite version is the recommended one, I got asked that | repeatedly on the python developer list, and couldn't really answer. My answer is the most recent has the most bugs fixed. New ones may appear but 99.999% of the time they are in new features. | You seem to be better informed in | low-level SQLite matters, would you recommend that I update the DLL? On Windows you definitely want to be on 3.3.6 or higher. Stupid virus scanners, backup agents, indexing software and the plethora of other crud running on a typical Windows desktop like to open files applications have just closed which then prevents the applications from doing other things to the files such as deleting or renaming them. (The last corporate PC I used wouldn't let me do complete Subversion checkouts due to the stupid backup agent interfering). 3.3.7 introduced new features which you don't want people to see for version stability purposes. 3.3.8 has virtual tables API changes and the virtual tables code isn't mature yet, especially error handling and memory issues. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFdpWTmOOfHg372QQRAnoLAJ96M4tnvmkL+Z+BgxMK98jniNR8EwCgtg9F OF8kION10PcAA1RSp28wkoo= =7ryw -----END PGP SIGNATURE----- _______________________________________________ pysqlite mailing list [email protected] http://lists.initd.org/mailman/listinfo/pysqlite