Age | Commit message (Collapse) | Author | Files | Lines |
|
3.34.0-r1
Windows MSI installer files are now provided in addition to the exe files (APSW issue 294), as well as wheels for Python 3.6+. Python 3.9 binaries are also now available. The wheels can be installed via pip.
Added Connection.txn_state()
Added constants:
SQLITE_IOERR_CORRUPTFS
|
|
|
|
3.33.0-r1
Small performance improvement in string handling
apsw module exposes Cursor, Blob, and Backup types (APSW issue 273)
pkg-config is used to detect International Components for Unicode (ICU) sdk when the SQLite ICU extension <https://www.sqlite.org/src/artifact?ci=trunk&filename=ext/icu/README.txt>`___ is enabled. It falls back to icu-config as before..
Added constants:
SQLITE_OPEN_SUPER_JOURNAL
|
|
3.32.2-r1
Added constants:
SQLITE_IOERR_DATA, SQLITE_CORRUPT_INDEX, SQLITE_BUSY_TIMEOUT, SQLITE_FCNTL_CKPT_START, SQLITE_FCNTL_RESERVE_BYTES
|
|
|
|
|
|
3.31.1-r1
Various updates due to year change
Fix deprecated universal newline use in shell
Shell now uses pragma function_list to get list of functions for tab completion
Added constants:
SQLITE_DBCONFIG_TRUSTED_SCHEMA, SQLITE_DBCONFIG_LEGACY_FILE_FORMAT,
SQLITE_CONSTRAINT_PINNED, SQLITE_OK_SYMLINK, SQLITE_CANTOPEN_SYMLINK,
SQLITE_FCNTL_CKPT_DONE, SQLITE_OPEN_NOFOLLOW, SQLITE_VTAB_DIRECTONLY
|
|
3.30.1-r1
Added constants:
SQLITE_DBCONFIG_ENABLE_VIEW
Updated hashing of SQL statements
Python 3.8 Windows binaries available.
|
|
3.29.0:
Added constants:
SQLITE_DBCONFIG_DQS_DML, SQLITE_DBCONFIG_DQS_DDL, SQLITE_DBCONFIG_LEGACY_ALTER_TABLE
Updated Connection.config() with all current SQLITE_DBCONFIG constants. Also fixes APSW issue 249
|
|
3.28.0-r1
Added constant:
SQLITE_DBCONFIG_WRITABLE_SCHEMA
|
|
|
|
|
|
3.27.2-r1
Added constants:
* SQLITE_CONFIG_MEMDB_MAXSIZE, SQLITE_FCNTL_SIZE_LIMIT
Added support for the geopoly extension
Removed hash optimisation that isn’t useful any more
|
|
3.26.0-r1
Added constant:
SQLITE_DBCONFIG_DEFENSIVE
|
|
|
|
3.25.1:
Added constants:
SQLITE_INDEX_CONSTRAINT_FUNCTION, SQLITE_CANTOPEN_DIRTYWAL, SQLITE_ERROR_SNAPSHOT, SQLITE_FCNTL_DATA_VERSION
Shell output mode now has lines and columns for compatibility (APSW issue 214)
Example now runs under both Python 2 and 3.
|
|
3.24.0-r1
Added constants:
* SQLITE_DBCONFIG_RESET_DATABASE, and support for it in Connection.config()
* SQLITE_LOCKED_VTAB, and SQLITE_CORRUPT_SEQUENCE extended result codes
Added keywords and updated the shell to use it.
|
|
|
|
3.23.1:
Added constants:
SQLITE_DBSTATUS_CACHE_SPILL, SQLITE_FCNTL_LOCK_TIMEOUT
|
|
3.22.0:
Added constants:
SQLITE_DBCONFIG_TRIGGER_EQP, SQLITE_DBCONFIG_MAX
SQLITE_READONLY_CANTINIT, SQLITE_ERROR_RETRY, SQLITE_ERROR_MISSING_COLLSEQ, SQLITE_READONLY_DIRECTORY
|
|
|
|
|
|
3.21.0:
Added constants:
SQLITE_INDEX_CONSTRAINT_ISNULL, SQLITE_INDEX_CONSTRAINT_ISNOT,
SQLITE_INDEX_CONSTRAINT_ISNOTNULL, SQLITE_INDEX_CONSTRAINT_IS and
SQLITE_INDEX_CONSTRAINT_NE
SQLITE_CONFIG_SMALL_MALLOC
SQLITE_IOCAP_BATCH_ATOMIC
SQLITE_IOERR_ROLLBACK_ATOMIC, SQLITE_IOERR_COMMIT_ATOMIC and
SQLITE_IOERR_BEGIN_ATOMIC
SQLITE_FCNTL_COMMIT_ATOMIC_WRITE, SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE and
SQLITE_FCNTL_BEGIN_ATOMIC_WRITE
|
|
|
|
Added SQLITE_DBCONFIG_ENABLE_QPSG constant.
Added shell .open command (APSW issue 240)
|
|
|
|
No APSW changes.
Now we're in sync with databases/sqlite3
|
|
|
|
|
|
|
|
Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
|
|
|
|
Remove now unnecessary overrides in various packages.
|
|
|
|
APSW provides an SQLite 3 wrapper that provides the thinnest layer over
the SQLite database library possible. Everything you can do from the
SQLite C API, you can do from Python. Although APSW looks vaguely
similar to the PEP 249 (DBAPI), it is not compliant with that API
because instead it works the way SQLite 3 does.
|