Changelog for sqlite3-devel-3.7.8-13.1.x86_64.rpm :

* Fri Oct 07 2011 maxAATTsuse.com- New version 3.8:
* Orders of magnitude performance improvement for CREATE INDEX on very large tables.
* Improved the windows VFS to better defend against interference from anti-virus software.
* Improved query plan optimization when the DISTINCT keyword is present.
* Allow more system calls to be overridden in the unix VFS - to provide better support for chromium sandboxes.
* Increase the default size of a lookahead cache line from 100 to 128 bytes.
* Enhancements to the test_quota.c module so that it can track preexisting files.
* Bug fix: Virtual tables now handle IS NOT NULL constraints correctly.
* Bug fixes: Correctly handle nested correlated subqueries used with indices in a WHERE clause.- Re-integrate the Tcl bidings as a subpackage, now that it is easier to build both out of a single tarball.
* Thu Aug 04 2011 idonmezAATTnovell.com- New Version: 3.7.7.1:
* Fix a bug causing PRAGMA case_sensitive_like statements compiled using sqlite3_prepare() to fail with an SQLITE_SCHEMA error.
* Fri Jun 24 2011 maxAATTnovell.com- New Version: 3.7.7:
* Add support for URI filenames.
* Add the sqlite3_vtab_config() interface in support of ON CONFLICT clauses with virtual tables.
* Add the xSavepoint, xRelease and xRollbackTo methods in virtual tables in support of SAVEPOINT for virtual tables.
* Update the built-in FTS3/FTS4 and RTREE virtual tables to support ON CONFLICT clauses and REPLACE.
* Avoid unnecessary reparsing of the database schema.
* Added support for the FTS4 prefix option and the FTS4 order option.
* Allow WAL-mode databases to be opened read-only as long as there is an existing read/write connection.
* Added support for short filenames.
* Fri May 20 2011 maxAATTnovell.com- New Version: 3.7.6.3:
* Fix a problem with WAL mode which could cause transactions to silently rollback if the cache_size is set very small (less than 10) and SQLite comes under memory pressure.- Enabled the column metadata APIs (bnc#383370).
* Wed Apr 13 2011 maxAATTnovell.com- New Version: 3.7.6.1:
* Added the sqlite3_wal_checkpoint_v2() interface and enhanced the wal_checkpoint pragma to support blocking checkpoints.
* Improvements to the query planner so that it makes better estimates of plan costs and hence does a better job of choosing the right plan, especially when SQLITE_ENABLE_STAT2 is used.
* Fix a bug which prevented deferred foreign key constraints from being enforced when sqlite3_finalize() was not called by one statement with a failed foreign key constraint prior to another statement with foreign key constraints running.
* Integer arithmetic operations that would have resulted in overflow are now performed using floating-point instead.
* Increased the version number on the VFS object to 3 and added new methods xSetSysCall, xGetSysCall, and xNextSysCall used for doing full-coverage testing.
* Increase the maximum value of SQLITE_MAX_ATTACHED from 30 to 62 (though the default value remains at 10).
* Added the fts4aux table
* Added support for compressed FTS4 content
* Enhance the ANALYZE command to support the name of an index as its argument, in order to analyze just that one index.
* Added the \"unix-excl\" built-in VFS on unix and unix-like platforms.
* Thu Feb 03 2011 maxAATTnovell.com- New Version: 3.7.5:
* Added the sqlite3_vsnprintf() interface.
* Added the SQLITE_DBSTATUS_LOOKASIDE_HIT, SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE, and SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL options for the sqlite3_db_status() interface.
* Added the SQLITE_OMIT_AUTORESET compile-time option.
* Added the SQLITE_DEFAULT_FOREIGN_KEYS compile-time option.
* Updates to sqlite3_stmt_readonly() so that its result is well-defined for all prepared statements and so that it works with VACUUM.
* Added the \"-heap\" option to the command-line shell
* Fix a bug involving frequent changes in and out of WAL mode and VACUUM that could (in theory) cause database corruption.
* Enhance the sqlite3_trace() mechanism so that nested SQL statements such as might be generated by virtual tables are shown but are shown in comments and without parameter expansion. This greatly improves tracing output when using the FTS3/4 and/or RTREE virtual tables.
* Change the xFileControl() methods on all built-in VFSes to return SQLITE_NOTFOUND instead of SQLITE_ERROR for an unrecognized operation code.
* The SQLite core invokes the SQLITE_FCNTL_SYNC_OMITTED file control to the VFS in place of a call to xSync if the database has PRAGMA synchronous set to OFF.- Split off sqlite3-tcl into a separate source package.
* Thu Jan 13 2011 maxAATTnovell.com- Adjust the package to the new upstream tarball naming and version numbering scheme.- New version: 3.7.4:
* Added the sqlite3_blob_reopen() interface to allow an existing sqlite3_blob object to be rebound to a new row.
* Use the new sqlite3_blob_reopen() interface to improve the performance of FTS.
* VFSes that do not support shared memory are allowed to access WAL databases if PRAGMA locking_mode is set to EXCLUSIVE.
* Enhancements to EXPLAIN QUERY PLAN.
* Added the sqlite3_stmt_readonly() interface.
* Added PRAGMA checkpoint_fullfsync.
* Added the SQLITE_FCNTL_FILE_POINTER option to sqlite3_file_control().
* Added support for FTS4 and enhancements to the FTS matchinfo() function.
* Added the test_superlock.c module which provides example code for obtaining an exclusive lock to a rollback or WAL database.
* Added the test_multiplex.c module which provides an example VFS that provides multiplexing (sharding) of a DB, splitting it over multiple files of fixed size.
* A very obscure bug associated with the or optimization was fixed.
* Wed Nov 17 2010 maxAATTnovell.com- New version: 3.7.3:
* Added the sqlite3_create_function_v2() interface that includes a destructor callback.
* Added support for custom r-tree queries using application-supplied callback routines to define the boundary of the query region.
* The default page cache strives more diligently to avoid using memory beyond what is allocated to it by SQLITE_CONFIG_PAGECACHE. Or if using page cache is allocating from the heap, it strives to avoid going over the sqlite3_soft_heap_limit64(), even if SQLITE_ENABLE_MEMORY_MANAGEMENT is not set.
* Added the sqlite3_soft_heap_limit64() interface as a replacement for sqlite3_soft_heap_limit().
* The ANALYZE command now gathers statistics on tables even if they have no indices.
* Tweaks to the query planner to help it do a better job of finding the most efficient query plan for each query.
* Enhanced the internal text-to-numeric conversion routines so that they work with UTF8 or UTF16, thereby avoiding some UTF16-to-UTF8 text conversions.
* Fix a problem that was causing excess memory usage with large WAL transactions in win32 systems.
* The interface between the VDBE and B-Tree layer is enhanced such that the VDBE provides hints to the B-Tree layer letting the B-Tree layer know when it is safe to use hashing instead of B-Trees for transient tables.
* Miscellaneous documentation enhancements.
* Fri Aug 27 2010 maxAATTnovell.com- New version: 3.7.2:
* Added new commands SQLITE_DBSTATUS_SCHEMA_USED and SQLITE_DBSTATUS_STMT_USED to the sqlite3_db_status() interface, in order to report out the amount of memory used to hold the schema and prepared statements of a connection.
* Increase the maximum size of a database pages from 32KiB to 64KiB.
* Use the LIKE optimization even if the right-hand side string contains no wildcards.
* Added the SQLITE_FCNTL_CHUNK_SIZE verb to the sqlite3_file_control() interface for both unix and windows, to cause database files to grow in large chunks in order to reduce disk fragmentation.
* Fixed a bug in the query planner that caused performance regresssions relative to 3.6.23.1 on some complex joins.
* Fixed a typo in the OS/2 backend.
* Refactored the pager module.
* The SQLITE_MAX_PAGE_SIZE compile-time option is now silently ignored. The maximum page size is hard-coded at 65536 bytes.
* Fix an old and very obscure bug that can lead to corruption of the database free-page list when incremental_vacuum is used.
* Thu Aug 05 2010 maxAATTsuse.de- New version 3.7.0.1:
* Fix a potential database corruption problem that can result if the same database file is alternately written by version 3.7.0 and 3.6.23.1.
* Fix a possible performance regression caused by the introduction of automatic indexing.