Apsw

========

You can use this release against any release of SQLite 3.

SQLite 3.2.2 API removed *sqlite3_global_recover*. That function
was not wrapped in APSW. Note that SQLite 3.2.2 contains a bug fix
that applies when you use 64 bit integer primary keys (32 bit ints are
fine).

========

You can use this release against any release of SQLite 3.

There are no changes in APSW except to correct an error in the example
code (collations are registered against the connection not the cursor)

SQLite 3.2.1 had one addition in the stable C API, which was a new
function named *sqlite3_global_recover*. That function is not
applicable for wrapping in APSW.

========

You can use this release against any release of SQLite 3.

The text string returned by apsw.Error used to say
"apsw.APSWException" and has been changed to "apsw.Error". This is
purely cosmetic and helps make clear what the class is. (The old
string was what the original class name was in an earlier version of
the code.)

Added *SQLITE_ALTER_TABLE* and *SQLITE_REINDEX*
constants for the authorizer function. (These constants were
introduced in SQLite 3.1.3).

Changed various C++-isms into standard C (eg // comments and the
placing of some *CHECK_THREAD* macro calls).

Added module level function :meth:`~apsw.apsw_version` which returns
the version of APSW.

SQLite 3.1.3 had no changes in the stable C API other than what is
mentioned above. There were some new experimental functions added
which are not currently documented on the SQLite website, which are
not wrapped by APSW. Please contact me if you believe they will
remain in SQLite and you would like them wrapped:

* *sqlite3_sleep* An alternative function which sleeps for a
specified number of milliseconds can be provided. By default SQLite
just uses the standard operating system call.
* *sqlite3_expired* This function is internal to statement
execution. It would apply to the implementation of
:meth:`Cursor.executemany` and could in theory provide a marginal
improvement in performance.
* A global variable *sqlite3_temp_directory* can be used before
any databases are opened to set where temporary files are created. By
default SQLite just uses the standard operating system mechanisms.

========

There are no functional changes. The only changes were to correct some
variable names in the example code (they were cut and pasted from the
test code which used different names) and to make the source zip file
extract its contents into a sub-directory which is the more typical
way of packaging that sort of thing.

========

All remaining functionality in the C API for SQLite 3.0.8 is now
available.

Finished this documentation.

========

Initial release

.. _renaming:

Renaming
--------

Early APSW exposed some method and attribute names not complying with
Python naming conventions as documented in :pep:`8`. For example
``exceptionfor`` instead of ``exception_for``. This has now been
corrected with the compliant names being documented and used in
examples. The old names are still available maintaining
:ref:`backwards compatibility <backcompat>`.

The change happened in version 3.43.2.0.

.. include:: ../doc/renames.rstgen