[pysqlite] APSW 3.6.6.2-r1 released

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

APSW 3.6.6.2-r1 is now available.  Full documentation including change
history is available at http://apsw.googlecode.com/svn/publish/index.html

The project is hosted at http://code.google.com/p/apsw/ where you will
find downloads, source control system, bug tracker etc.

There was discussion a week ago on this list about tracing SQL execution
without having to change your source.  This is now available as part of
APSW.  The documentation shows help information and sample output:

http://apsw.googlecode.com/svn/publish/execution.html#apsw-trace

Windows binary download for Python 3.0 is available.

Various changes in data structures and containers to reduce code size.

Changed the code to handle SQLite errors to only use Python
functionality and no operating system functionality (thread local
storage). This also addresses issue 36 where Vista was not binary
compatible with XP. Thanks to Rudolf Gaertner for assistance in
detecting and diagnosing this issue.

Connections, cursors and blobs can be used by weak references.

You can now install Connection wide execution and row tracers.

The callbacks for execution and row tracers have a different signature
to include the cursor the execution or row happened on. This is a
backwards incompatible change. See tracing for details.

Due to popular demand, added Cursor.fetchall(). This is a longer way of
typing list(cursor).

Added attributes to the Connection class - filename, open_flags and
open_vfs. These let you track how the database was opened.

Revert to using older SQLite APIs in order to work around SQLite ticket
2158. (This also saves a little bit of SQLite memory usage). The user
visible effect was that you could get different exceptions and error
text depending on whether a query was already in the statement cache or
if you were multi-threading. As an example, if you have a query that
used an unknown collation then SQLite’s prepare returns SQLITE_ERROR
with error text about the bad collation. If a query had already been
prepared, the collation removed and then run the new SQLite routines are
returning SQLITE_SCHEMA and generic schema changed error text. Changing
user defined functions could also cause a previously correct query to
become invalid.

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

iEYEARECAAYFAkk5sK4ACgkQmOOfHg372QRHrwCfdJRViGQCsHj4SwF0MBmqyAWp
t3UAoLTyCtwVqDTu34X5NVx2nxJ9nhWV
=erk1
-----END PGP SIGNATURE-----
_______________________________________________
list-pysqlite mailing list
[email protected]
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite