[pysqlite] APSW 3.5.9-r1 released

Roger Binns <[email protected]> Sun, 01 Jun 2008 17:48:17 -0700
Newsgroups gmane.comp.python.db.pysqlite.user
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://code.google.com/p/apsw/

This requires SQLite 3.5.9 or later.

The major feature *not* in this release is support for SQLite's vfs.  I
wrote most of the code before DRH said he would be radically changing
the SQLite vfs api :-)  I will be picking this up again for SQLite 3.6.

SQLite 3.5 removed the requirement that all operations on a Connection
be done with the same thread.  This APSW release also removes that
requirement.  This also removes the requirement to call close which used
to be required to ensure it ran in the correct thread.

Incremental blob I/O is now present so you can treat blobs as though
they were a file.  Zeroblob is also allowed.

New constants were added as appropriate.

In addition to APSW's checking that 64 Python values won't hurt SQLite
(which is fundamentally a 32 bit database even in a 64 bit process),
SQLite's limit api is also exposed so you can set your own limits such
as when you are running somewhat untrusted SQL code.

The documented (and preferred) mechanism of including SQLite is to use
the amalgamation.  This includes the library within the APSW extension
and makes all the symbols private.  That makes life considerably easier
on Macs and also allows multiple versions of SQLite to be in the same
process address space without collisions.

The statement cache now defaults to the same size as pysqlite although
you can override with the value of your choosing including none at all.

sqlite3_collation_needed() was wrapped so you can supply collations on
demand.

Several bugs or inconsistencies were fixed.  Thanks to the people who
reported them.

http://code.google.com/p/apsw/issues/detail?id=15
The GIL is released around calls to sqlite3_prepare.

http://code.google.com/p/apsw/issues/detail?id=4
Error message text clearing was reported on to SQLite where they fixed it

http://code.google.com/p/apsw/issues/detail?id=1
Quoting issue caused example code virtual table failure on Windows

http://code.google.com/p/apsw/issues/detail?id=7
Filenames for extensions were not being converted to utf8

Roger


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIQ0NRmOOfHg372QQRAn8MAJ9A3gLrM5bSgUx2GWWB+Z8mnRK7VACbBVaB
nrj2+RgOKNjWqecg+mS9pis=
=KoZ3
-----END PGP SIGNATURE-----