pkgsrc/databases/sqlite3, branch cube-native-xorg

Changes 3.6.2:

2008-09-07T14:04:01Z

* Split the pager subsystem into separate pager and pcache subsystems. * Factor out indentifier resolution procedures into separate files. * Bug fixes.

Changes 3.6.1:

2008-08-18T12:29:20Z

* Added the lookaside memory allocator for a speed improvement in excess of 15% on some workloads. (Your mileage may vary.) * Added the SQLITE_CONFIG_LOOKASIDE verb to sqlite3_config() to control the default lookaside configuration. * Added verbs SQLITE_STATUS_PAGECACHE_SIZE and SQLITE_STATUS_SCRATCH_SIZE to the sqlite3_status() interface. * Modified SQLITE_CONFIG_PAGECACHE and SQLITE_CONFIG_SCRATCH to remove the "+4" magic number in the buffer size computation. * Added the sqlite3_db_config() and sqlite3_db_status() interfaces for controlling and monitoring the lookaside allocator separately on each database connection. * Numerious other performance enhancements * Miscellaneous minor bug fixes

Changes 3.6.0:

2008-07-18T17:43:34Z

* Modifications to the virtual file system interface to support a wider range of embedded systems. * All C-preprocessor macros used to control compile-time options now begin with the prefix "SQLITE_". * The SQLITE_MUTEX_APPDEF compile-time option is no longer supported. * The handling of IN and NOT IN operators that contain a NULL on their right-hand side expression is brought into compliance with the SQL standard and with other SQL database engines. This is a bug fix, but as it has the potential to break legacy applications that depend on the older buggy behavior. * The result column names generated for compound subqueries have been simplified to show only the name of the column of the original table and omit the table name. This makes SQLite operate more like other SQL database engines. * Added the sqlite3_config() interface for doing run-time configuration of the entire SQLite library. * Added the sqlite3_status() interface used for querying run-time status information about the overall SQLite library and its subsystems. * Added the sqlite3_initialize() and sqlite3_shutdown() interfaces. * The SQLITE_OPEN_NOMUTEX option was added to sqlite3_open_v2(). * Added the PRAGMA page_count command. * Added the sqlite3_next_stmt() interface. * Added a new R*Tree virtual table

Changes 3.5.9:

2008-05-25T07:11:13Z

* Added experimental support for the journal_mode PRAGMA and persistent journal. * Journal mode PERSIST is the default behavior in exclusive locking mode. * Fix a performance regression on LEFT JOIN (see ticket #3015) that was mistakenly introduced in version 3.5.8. * Performance enhancement: Reengineer the internal routines used to interpret and render variable-length integers. * Fix a buffer-overrun problem in sqlite3_mprintf() which occurs when a string without a zero-terminator is passed to "%.*s". * Always convert IEEE floating point NaN values into NULL during processing. * Make sure that when a connection blocks on a RESERVED lock that it is able to continue after the lock is released. * The "configure" scripts should now automatically configure unix systems for large file support. Improved error messages for when large files are encountered and large file support is disabled. * Avoid cache pages leaks following disk-full or I/O errors * And, many more minor bug fixes and performance enhancements...

Update to 3.5.6:

2008-03-04T10:46:55Z

2008 Feb 6 (3.5.6) * Fix a bug ( ticket #2913) that prevented virtual tables from working in a LEFT JOIN. The problem was introduced into shortly before the 3.5.5 release. * Bring the OS/2 porting layer up-to-date. * Add the new sqlite3_result_error_code() API and use it in the implementation of ATTACH so that proper error codes are returned when an ATTACH fails. 2008 Jan 31 (3.5.5) * Convert the underlying virtual machine to be a register-based machine rather than a stack-based machine. The only user-visible change is in the output of EXPLAIN. * Add the build-in RTRIM collating sequence. 2007 Dec 14 (3.5.4) * Fix a critical bug in UPDATE or DELETE that occurs when an OR REPLACE clause or a trigger causes rows in the same table to be deleted as side effects. (See ticket #2832.) The most likely result of this bug is a segmentation fault, though database corruption is a possibility. * Bring the processing of ORDER BY into compliance with the SQL standard for case where a result alias and a table column name are in conflict. Correct behavior is to prefer the result alias. Older versions of SQLite incorrectly picked the table column. (See ticket #2822.) * The VACUUM command preserves the setting of the legacy_file_format pragma. ( Ticket #2804.) * Productize and officially support the group_concat() SQL function. * Better optimization of some IN operator expressions. * Add the ability to change the auto_vacuum status of a database by setting the auto_vaccum pragma and VACUUMing the database. * Prefix search in FTS3 is much more efficient. * Relax the SQL statement length restriction in the CLI so that the ".dump" output of databases with very large BLOBs and strings can be played back to recreate the database. * Other small bug fixes and optimizations. 2007 Nov 27 (3.5.3) * Move website and documentation files out of the source tree into a separate CM system. * Fix a long-standing bug in INSERT INTO ... SELECT ... statements where the SELECT is compound. * Fix a long-standing bug in RAISE(IGNORE) as used in BEFORE triggers. * Fixed the operator precedence for the ~ operator. * On win32, do not return an error when attempting to delete a file that does not exist. * Allow collating sequence names to be quoted. * Modify the TCL interface to use sqlite3_prepare_v2(). * Fix multiple bugs that can occur following a malloc() failure. * sqlite3_step() returns SQLITE_MISUSE instead of crashing when called with a NULL parameter. * FTS3 now uses the SQLite memory allocator exclusively. The FTS3 amalgamation can now be appended to the SQLite amalgamation to generate a super-amalgamation containing both. * The DISTINCT keyword now will sometimes use an INDEX if an appropriate index is available and the optimizer thinks its use might be advantageous.

The new thread-safe feature doesn't really work: The py-sqlite2

2007-11-15T14:11:53Z

self-test fails with a segmentation fault.

Updated sqlite to 3.5.2. The main reason to update was that on Solaris,

2007-11-15T10:39:18Z

the file lemon.c uses the same identifiers (B_TRUE, B_FALSE) as the header, and therefore fails to build. Changes since 3.4.2: 2007 Nov 05 (3.5.2) * Dropped support for the SQLITE_OMIT_MEMORY_ALLOCATION compile-time option. * Always open files using FILE_FLAG_RANDOM_ACCESS under windows. * The 3rd parameter of the built-in SUBSTR() function is now optional. * Bug fix: do not invoke the authorizer when reparsing the schema after a schema change. * Added the experimental malloc-free memory allocator in mem3.c. * Virtual machine stores 64-bit integer and floating point constants in binary instead of text for a performance boost. * Fix a race condition in test_async.c. * Added the ".timer" command to the CLI 2007 Oct 04 (3.5.1) * Nota Bene: We are not using terms "alpha" or "beta" on this release because the code is stable and because if we use those terms, nobody will upgrade. However, we still reserve the right to make incompatible changes to the new VFS interface in future releases. * Fix a bug in the handling of SQLITE_FULL errors that could lead to database corruption. [11]Ticket #2686. * The test_async.c drive now does full file locking and works correctly when used simultaneously by multiple processes on the same database. * The CLI ignores whitespace (including comments) at the end of lines * Make sure the query optimizer checks dependences on all terms of a compound SELECT statement. [12]Ticket #2640. * Add demonstration code showing how to build a VFS for a raw mass storage without a filesystem. * Added an output buffer size parameter to the xGetTempname() method of the VFS layer. * Sticky SQLITE_FULL or SQLITE_IOERR errors in the pager are reset when a new transaction is started. 2007 Sep 04 (3.5.0) alpha * Redesign the OS interface layer. See [13]34to35.html for details. *** Potentially incompatible change *** * The [14]sqlite3_release_memory(), [15]sqlite3_soft_heap_limit(), and [16]sqlite3_enable_shared_cache() interfaces now work cross all threads in the process, not just the single thread in which they are invoked. *** Potentially incompatible change *** * Added the [17]sqlite3_open_v2() interface. * Reimplemented the memory allocation subsystem and made it replacable at compile-time. * Created a new mutex subsystem and made it replacable at compile-time. * The same database connection may now be used simultaneously by separate threads.

Update to 3.4.2:

2007-09-15T09:17:43Z

While stress-testing the soft_heap_limit feature, a bug that could lead to database corruption was discovered and fixed. Though the consequences of this bug are severe, the chances of hitting it in a typical application are remote. Upgrading is recommended only if you use the sqlite3_soft_heap_limit interface.

update to 3.4.1

2007-08-13T17:27:30Z

This release fixes a bug in VACUUM that can lead to database corruption. The bug was introduced in version 3.3.14. Upgrading is recommended for all users. Also included are a slew of other more routine enhancements and bug fixes. pkgsrc note: 3 selftests are failing due to some loss of accuracy in floating point calculations. The upstream fix is to disable the selftests in question (see sqlite ticket #2570).

Update to 3.4.0:

2007-07-03T17:29:57Z

2007 June 18 (3.4.0) * Fix a bug that can lead to database corruption if an SQLITE_BUSY error occurs in the middle of an explicit transaction and that transaction is later committed. Ticket #2409. See the CorruptionFollowingBusyError wiki page for details. * Fix a bug that can lead to database corruption if autovacuum mode is on and a malloc() failure follows a CREATE TABLE or CREATE INDEX statement which itself follows a cache overflow inside a transaction. See ticket #2418. * Added explicit upper bounds on the sizes and quantities of things SQLite can process. This change might cause compatibility problems for applications that use SQLite in the extreme, which is why the current release is 3.4.0 instead of 3.3.18. * Added support for Incremental BLOB I/O. * Added the zeroblob API and the zeroblob() SQL function. * Added support for Incremental Vacuum. * Added the SQLITE_MIXED_ENDIAN_64BIT_FLOAT compile-time option to suppport ARM7 processors with goofy endianness. * Removed all instances of sprintf() and strcpy() from the core library. * Added support for International Components for Unicode (ICU) to the full-text search extensions. * In the windows OS driver, reacquire a SHARED lock if an attempt to acquire an EXCLUSIVE lock fails. Ticket #2354 * Fix the REPLACE() function so that it returns NULL if the second argument is an empty string. Ticket #2324. * Document the hazards of type coversions in sqlite3_column_blob() and related APIs. Fix unnecessary type conversions. Ticket #2321. * Internationalization of the TRIM() function. Ticket #2323 * Use memmove() instead of memcpy() when moving between memory regions that might overlap. Ticket #2334 * Fix an optimizer bug involving subqueries in a compound SELECT that has both an ORDER BY and a LIMIT clause. Ticket #2339. * Make sure the sqlite3_snprintf() interface does not zero-terminate the buffer if the buffer size is less than 1. Ticket #2341 * Fix the built-in printf logic so that it prints "NaN" not "Inf" for floating-point NaNs. Ticket #2345 * When converting BLOB to TEXT, use the text encoding of the main database. Ticket #2349 * Keep the full precision of integers (if possible) when casting to NUMERIC. Ticket #2364 * Fix a bug in the handling of UTF16 codepoint 0xE000 * Consider explicit collate clauses when matching WHERE constraints to indices in the query optimizer. Ticket #2391 * Fix the query optimizer to correctly handle constant expressions in the ON clause of a LEFT JOIN. Ticket #2403 * Fix the query optimizer to handle rowid comparisions to NULL correctly. Ticket #2404 * Fix many potental segfaults that could be caused by malicious SQL statements.