Apsw

Latest version: v3.47.2.0

Safety actively analyzes 687959 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 18 of 24

3.7.4r1

========

Binary downloads for Windows 64 bit Python versions 2.6 and above
including Python 3 are now available.

:meth:`apsw.soft_heap_limit` now uses `sqlite3_soft_heap_limit64
<https://sqlite.org/c3ref/soft_heap_limit64.html>`__ so you can
provide values larger than 2GB. It is now also able to return the
previous value instead of None.

Improve getting shell timer information for 64 bit Windows.

:meth:`Blob.reopen` is implemented.

FTS4 is enabled and in the binary builds. Note that it is an
augmentation of FTS3 rather than totally separate code and described
in the `SQLite documentation
<https://sqlite.org/fts3.html#fts4>`__.

3.7.3r1

========

You can read blobs into pre-existing buffers using
:meth:`Blob.read_into`. (This is more efficient than allocating new
buffers as :meth:`Blob.read` does and then copying.) (:issue:`109`).

Fixed bug with unicode output in CSV mode in the shell.

`sqlite_create_function_v2
<https://sqlite.org/c3ref/create_function.html>`__ now means that some
housekeeping APSW did can be pushed back onto SQLite and the
consequent deletion of some code

3.7.2r1

========

No changes to APSW. Upgrading to this version of SQLite is
`recommended <https://sqlite.org/releaselog/3_7_2.html>`__.

3.7.1r1

========

Updated various constants including `SQLITE_FCNTL_CHUNK_SIZE
<https://sqlite.org/c3ref/c_fcntl_chunk_size.html>`__ used with
:meth:`Connection.file_control`.

Fixed Unicode output with some file objects from the shell (:issue:`108`).

With the shell, you can specify handling of characters not present in
the output encoding (eg replace to use '?' or similar, ignore,
xmlcharrefreplace etc). For example::

.encoding cp437:replace

3.7.0.1r1

==========

Fixed issue when using a tracer and a context manager fails to commit.

3.7.0r1

========

Added several new constants.

`Write Ahead Logging <https://sqlite.org/wal.html>`__ is
:ref:`supported <wal>`. You can make all databases automatically use
WAL mode if available by using :ref:`connection hooks <wal>`.

Added :meth:`format_sql_value` for generating a SQL syntax string from
a value. This is implemented in C and is significantly faster than
doing the same formatting in Python.

Using the above function and other tweaks the :ref:`shell` dumper is
now three to four times faster. Thanks to Nikolaus Rath for pointing
out the problem and providing test data.

The shell now does colour highlighting making it easy to visually
distinguish prompts, errors, headers and value types when outputting
to a terminal. See the `--no-colour` argument and **.colour**
command. Those of you in the two countries that have not adopted the
metric system may also omit the 'u'. For Windows users you won't get
colour output unless you install `colorama
<https://pypi.python.org/pypi/colorama>`__

When using the context manager (with statement) of a
:class:`Connection` and the exit commit had an error, then the
transaction is rolled back. This could occur if SQLite had buffered
the transaction entirely in memory and a non-eager transaction lock
had been obtained. Thanks to Geoff Ness for finding the problem.
(:issue:`98`).

Fixed bug when an error is returned creating an instance of a virtual
table (eg an invalid column name). Before the fix you would get the
previous error message or a crash. Thanks to Jose Gomes for finding
the problem. :issue:`103`

There is now a PPA for Ubuntu users that is kept up to date with APSW
and SQLite at \https://launchpad.net/~ubuntu-rogerbinns/+archive/apsw
which has the latest SQLite embedded statically inside (ie system
SQLite is ignored) and has all the extensions enabled: FTS3, RTree,
ICU, asyncvfs

If you open VFS files directly then the filename is always run through
xFullPathname first. SQLite guarantees this behaviour but the
existing VFS code was not doing that for direct opens. Opens from
SQLite were doing it.

Fixed error where :attr:`apsw.connection_hooks` were being run before
the :ref:`statement cache <statementcache>` was initialised which would
result in a crash if any hooks executed SQL code.

Page 18 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.