2016-11-04 (3.15.1)

Fix the VACUUM command so that it spills excess content to disk rather
than holding everything in memory, and possible causing an out-of-memory
error for larger database files. This fixes an issue introduced by
version 3.15.0.

Fix a case (present since 3.8.0 - 2013-08-26)
where OR-connected terms in the ON clause of a LEFT JOIN
might cause incorrect results. Ticket
34a579141b2c5ac.

Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE
clause references a non-existent collating sequence. Ticket
e8d439c77685eca6.

Improved the cost estimation for an index scan which includes a WHERE clause
that can be partially or fully evaluated using columns in the index and without
having to do a table lookup. This fixes a performance regression that occurred
for some obscure queries following the ORDER BY LIMIT optimization introduced
in version 3.12.0.

Change the temporary directory search algorithm on Unix to allow directories with
write and execute permission, but without read permission, to serve as temporary
directories. Apply this same standard to the "." fallback directory.

Bug Fixes:

Fix a problem with the multi-row one-pass DELETE optimization that was
causing it to compute incorrect answers with a self-referential subquery in
the WHERE clause. Fix for ticket
dc6ebeda9396087

Fix a possible segfault with DELETE when table is a rowid table with an
INTEGER PRIMARY KEY and the WHERE clause contains a OR and
the table has one or more indexes that are able to trigger the OR optimization,
but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY.
Ticket 16c9801ceba49.

When checking for the WHERE-clause push-down optimization, verify that all terms
of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket
f7f8c97e97597.

Fix a locking race condition in Windows that can occur when two or more processes
attempt to recover the same hot journal at the same time.

Fix a 16-month-old bug in the query planner that could generate incorrect results
when a scalar subquery attempts to use the block sorting optimization. Ticket
cb3aa0641d9a4.

2016-04-18 (3.12.2)

Fix a backwards compatibility problem in version 3.12.0 and 3.12.1:
Columns declared as "INTEGER" PRIMARY KEY (with quotes around
the datatype keyword) were not being recognized as an
INTEGER PRIMARY KEY, which resulted in an incompatible database file.
Ticket 7d7525cb01b68

The query planner is able to optimize IN operators on virtual tables
even if the xBestIndex method does not set the
sqlite3_index_constraint_usage.omit flag of the
virtual table column to the left of the IN operator.

The query planner now does a better job of optimizing virtual table
accesses in a 3-way or higher join where constraints on the virtual
table are split across two or more other tables of the join.

Enhance the 'utc' modifier in the date and time functions so that it is a no-op if
the date/time is known to already be in UTC. (This is not a compatibility break since
the behavior has long been documented as "undefined" in that case.)

Added the --enable-editline and --enable-static-shell options
to the various autoconf-generated configure scripts.

Omit all use of "awk" in the makefiles, to make building easier for MSVC users.

Important fixes:

Fix inconsistent integer to floating-point comparison operations that
could result in a corrupt index if the index is created on a table
column that contains both large integers and floating point values
of similar magnitude. Ticket
38a97a87a6.

Enhance the page cache so that it can preallocate a block of memory to
use for the initial set page cache lines. Set the default preallocation
to 100 pages. Yields about a 5% performance increase on common workloads.

Miscellaneous micro-optimizations result in 22.3% more work for the same
number of CPU cycles relative to the previous release.
SQLite now runs twice as fast as version 3.8.0 and three times as
fast as version 3.3.9.
(Measured using
cachegrind on the
speedtest1.c workload on
Ubuntu 14.04 x64 with gcc 4.8.2 and -Os. Your performance may vary.)

2015-05-20 (3.8.10.2)

Fix an index corruption issue introduced by version 3.8.7. An index
with a TEXT key can be corrupted by an INSERT into the corresponding
table if the table has two nested triggers that convert the key value to INTEGER
and back to TEXT again.
Ticket 34cd55d68e0

2015-01-20 (3.8.8.1)

Fix a bug in the sorting logic, present since version 3.8.4, that can cause
output to appear in the wrong order on queries that contains an ORDER BY clause,
a LIMIT clause, and that have approximately 60 or more columns in the result set.
Ticket f97c4637102a3ae72b79.

Ensure durability following a power loss with
"PRAGMA journal_mode=TRUNCATE" by calling fsync() right after truncating
the journal file.

The query planner now recognizes that any column in the right-hand
table of a LEFT JOIN can be NULL, even if that column has a NOT NULL
constraint. Avoid trying to optimize out NULL tests in those cases.
Fix for ticket
6f2222d550f5b0ee7ed.

Make sure ORDER BY puts rows in ascending order even if the DISTINCT
operator is implemented using a descending index. Fix for ticket
c5ea805691bfc4204b1cb9e.

Fix data races that might occur under stress when running with many threads
in shared cache mode where some of the threads are opening and
closing connections.

2014-12-05 (3.8.7.3)

Bug fix: Ensure the cached KeyInfo objects (an internal abstraction not visible to the
application) do not go stale when operating in shared cache mode and frequently closing
and reopening some database connections while leaving other database connections on the
same shared cache open continuously. Ticket
e4a18565a36884b00edf.

Bug fix: Recognize that any column in the right-hand table of a LEFT JOIN can be
NULL even if the column has a NOT NULL constraint. Do not apply optimizations that
assume the column is never NULL. Ticket
6f2222d550f5b0ee7ed.

2014-11-18 (3.8.7.2)

Enhance the ROLLBACK command so that pending queries are allowed to continue as long
as the schema is unchanged. Formerly, a ROLLBACK would cause all pending queries to
fail with an SQLITE_ABORT or SQLITE_ABORT_ROLLBACK error. That error is still returned
if the ROLLBACK modifies the schema.

Bug fix: Make sure that NULL results from OP_Column are fully and completely NULL and
do not have the MEM_Ephem bit set.
Ticket 094d39a4c95ee4.

Bug fix: The %c format in sqlite3_mprintf() is able to handle precisions greater than 70.

Bug fix: Do not automatically remove the DISTINCT keyword from a SELECT that forms
the right-hand side of an IN operator since it is necessary if the SELECT also
contains a LIMIT.
Ticket db87229497.

2014-10-17 (3.8.7)

Performance Enhancements:

Many micro-optimizations result in 20.3% more work for the same number
of CPU cycles relative to the previous release.
The cumulative performance increase since version 3.8.0 is 61%.
(Measured using
cachegrind on the
speedtest1.c workload on
Ubuntu 13.10 x64 with gcc 4.8.1 and -Os. Your performance may vary.)

The sorter can use auxiliary helper threads to increase real-time response.
This feature is off by default and may be
enabled using the PRAGMA threads command or the SQLITE_DEFAULT_WORKER_THREADS
compile-time option.

Enhance the skip-scan optimization so that it is able to skip index terms that
occur in the middle of the index, not just as the left-hand side of the index.

Fix a bug in the partial index implementation that might result in an incorrect
answer if a partial index is used in a subquery or in a view.
Ticket 98d973b8f5.

Fix a query planner bug that might cause a table to be scanned in the wrong direction
(thus reversing the order of output) when a DESC index is used to implement the ORDER BY
clause on a query that has an identical GROUP BY clause.
Ticket ba7cbfaedc7e6.

Show ASCII-art abstract syntax tree diagrams using the ".selecttrace"
and ".wheretrace" commands in the
command-line shell when compiled with SQLITE_DEBUG, SQLITE_ENABLE_SELECTTRACE,
and SQLITE_ENABLE_WHERETRACE. Also provide the sqlite3TreeViewExpr() and
sqlite3TreeViewSelect() entry points that can be invoked from with the
debugger to show the parse tree when stopped at a breakpoint.

Drop support for SQLITE_ENABLE_TREE_EXPLAIN. The SELECTTRACE mechanism provides
more useful diagnostics information.

New options to the command-line shell for configuring auxiliary
memory usage: --pagecache, --lookaside, and --scratch.

Add the capability of evaluating an IN operator as a sequence
of comparisons as an alternative to using a table lookup. Use the sequence
of comparisons implementation in circumstances where it is likely to be
faster, such as when the right-hand side of the IN operator
is small and/or changes frequently.

ORDER BY ignored if the query has an identical GROUP BY.
Ticket b75a9ca6b0

The group_concat(x,'') SQL function returns NULL instead of an empty string
when all inputs are empty strings.
Ticket 55746f9e65

Fix a bug in the VDBE code generator that caused crashes when
doing an INSERT INTO ... SELECT statement where the number of columns
being inserted is larger than the number of columns in the destination
table.
Ticket e9654505cfd

Fix a problem in CSV import in the command-line shell
where if the leftmost field of the first row
in the CSV file was both zero bytes in size and unquoted no data would
be imported.

Fix a problem in FTS4 where the left-most column that contained
the notindexed column name as a prefix
was not indexed rather than the column whose name matched exactly.

Fix the sqlite3_db_readonly() interface so that it returns true if
the database is read-only due to the file format write version number
being too large.

Bug fix: Compute the correct answer for queries that contain an IS NOT NULL
term in the WHERE clause and also contain an OR term in the WHERE clause and
are compiled with SQLITE_ENABLE_STAT4.
Ticket [4c86b126f2]

Bug fix: Make sure "rowid" columns are correctly resolved in joins between
normal tables and WITHOUT ROWID tables.
Ticket [c34d0557f7]

Bug fix: Make sure the same temporary registers are not used in concurrent
co-routines used to implement compound SELECT statements containing ORDER
BY clauses, as such use can lead to incorrect answers.
Ticket [8c63ff0eca]

Bug fix: Repair a name-resolution error that can occur in sub-select statements
contained within a TRIGGER.
Ticket [4ef7e3cfca]

Bug fix: Fix column default values expressions of the form
"DEFAULT(-(-9223372036854775808))" so that they work correctly, initializing
the column to a floating point value approximately equal to
+9223372036854775808.0.

2014-02-03 (3.8.3)

Added SQLITE_DETERMINISTIC as an optional bit in the 4th argument to the
sqlite3_create_function() and related interfaces, providing applications with
the ability to create new functions that can be factored out of inner loops when
they have constant arguments.

Add SQLITE_READONLY_DBMOVED error code, returned at the beginning of a
transaction, to indicate that the underlying database file has been renamed
or moved out from under SQLite.

Allow arbitrary expressions, including function calls and subqueries, in
the filename argument to ATTACH.

2013-12-06 (3.8.2)

Changed the defined behavior for the CAST expression when floating point values
greater than +9223372036854775807 are cast into into integers so that the
result is the largest possible integer, +9223372036854775807, instead of
the smallest possible integer, -9223372036854775808. After this change,
CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead
of -9223372036854775808.
← Potentially Incompatible Change!

The sqlite3_analyzer utility program is updated to provide better descriptions
and to compute a more accurate estimate for "Non-sequential pages"

Refactor the implementation of PRAGMA statements to improve parsing performance.

The directory used to hold temporary files on unix can now be set using
the SQLITE_TMPDIR environment variable, which takes precedence over the
TMPDIR environment variable. The sqlite3_temp_directory global variable
still has higher precedence than both environment variables, however.

The SQLITE_BUSY_SNAPSHOT extended error code is returned in WAL mode when
a read transaction cannot be upgraded to a write transaction because the read is
on an older snapshot.

Enhancements to the sqlite3_analyzer utility program to provide size
information separately for each individual index of a table, in addition to
the aggregate size.

Allow read transactions to be freely opened and closed by SQL statements run
from within the implementation of application-defined SQL functions if the
function is called by a SELECT statement that does not access any database table.

Disable the use of posix_fallocate() on all (unix) systems unless the
HAVE_POSIX_FALLOCATE compile-time option is used.

Update the ".import" command in the command-line shell to support multi-line
fields and correct RFC-4180 quoting and to issue warning and/or error messages
if the input text is not strictly RFC-4180 compliant.

Bug fix: In the unicode61 tokenizer of FTS4, treat all private code points
as identifier symbols.

Bug fix: Bare identifiers in ORDER BY clauses bind more tightly to output column
names, but identifiers in expressions bind more tightly to input column names.
Identifiers in GROUP BY clauses always prefer output column names, however.

Bug fixes: Multiple problems in the legacy query optimizer were fixed by the
move to NGQP.

Increase the default value of SQLITE_MAX_SCHEMA_RETRY to 50 and make sure
that it is honored in every place that a schema change might force a statement
retry.

Add a new test harness called "mptester" used to verify correct operation
when multiple processes are using the same database file at the same time.

Enhance the extension loading mechanism to be more flexible (while
still maintaining backwards compatibility) in two ways:

If the default entry point "sqlite3_extension_init" is not present in
the loadable extension, also try an entry point "sqlite3_X_init" where
"X" is based on the shared library filename. This allows every extension
to have a different entry point, which allows them to be statically linked
with no code changes.

The shared library filename passed to sqlite3_load_extension() may
omit the filename suffix, and an appropriate architecture-dependent
suffix (".so", ".dylib", or ".dll") will be added automatically.

Added many new loadable extensions to the source tree, including
amatch, closure, fuzzer, ieee754, nextchar, regexp, spellfix,
and wholenumber. See header comments on each extension source file
for further information about what that extension does.

Enhance FTS3 to avoid using excess stack space when there are a huge
number of terms on the right-hand side of the MATCH operator. A side-effect
of this change is that the MATCH operator can only accommodate 12 NEAR
operators at a time.

Query planner enhancement: Use the transitive property of constraints
to move constraints into the outer loops of a join whenever possible,
thereby reducing the amount of work that needs to occur in inner loops.

Discontinue the use of posix_fallocate() on unix, as it does not work on all
filesystems.

Bug fix:
Only consider AS names from the result set as candidates for resolving
identifiers in the WHERE clause if there are no other matches. In the
ORDER BY clause, AS names take priority over any column names.
Ticket 2500cdb9be05

Bug fix: Do not allow a virtual table to cancel the ORDER BY clause unless
all outer loops are guaranteed to return no more than one row result.
Ticket ba82a4a41eac1.

Bug fix: Do not suppress the ORDER BY clause on a virtual table query if
an IN constraint is used.
Ticket f69b96e3076e.

Bug fix: The command-line shell gives an exit code of 0 when terminated
using the ".quit" command.

Bug fix: When a compound query that uses an ORDER BY clause
with a COLLATE operator, make sure that the sorting occurs
according to the specified collation and that the comparisons associate with
the compound query use the native collation. Ticket
6709574d2a8d8.

Bug fix: Makes sure the authorizer callback gets
a valid pointer to the string "ROWID" for the column-name parameter when
doing an UPDATE that changes the rowid. Ticket
0eb70d77cb05bb2272

Bug fix: Do not move WHERE clause terms inside OR expressions that are
contained within an ON clause of a LEFT JOIN. Ticket
f2369304e4

Bug fix: Make sure an error is always reported when attempting to preform
an operation that requires a collating sequence that is missing.
Ticket 0fc59f908b

2013-04-12 (3.7.16.2)

Fix a bug (present since version 3.7.13) that could result in database corruption
on windows if two or more processes try to access the same database file at the
same time and immediately after third process crashed in the middle of committing
to that same file. See ticket
7ff3120e4f for further
information.

2012-09-03 (3.7.14)

Drop built-in support for OS/2. If you need to upgrade an OS/2
application to use this or a later version of SQLite,
then add an application-defined VFS using the
sqlite3_vfs_register() interface. The code removed in this release can
serve as a baseline for the application-defined VFS.

Ensure that floating point values are preserved exactly when reconstructing
a database from the output of the ".dump" command of the
command-line shell.

Remove limits on the magnitude of precision and width value in the
format specifiers of the sqlite3_mprintf() family of string rendering
routines.

Fix a bug that prevent ALTER TABLE ... RENAME from working
on some virtual tables in a database with a UTF16 encoding.

Fix a bug in ASCII-to-float conversion that causes slow performance and
incorrect results when converting numbers with ridiculously large exponents.

Fix a bug that causes incorrect results in aggregate queries that use
multiple aggregate functions whose arguments contain complicated expressions
that differ only in the case of string literals contained within those
expressions.

Fix a bug that prevented the page_count and quick_check pragmas from
working correctly if their names were capitalized.

2011-04-13 (3.7.6.1)

Fix a bug in 3.7.6 that only appears if the SQLITE_FCNTL_SIZE_HINT
file control is used with a build of SQLite that makes use of the
HAVE_POSIX_FALLOCATE compile-time option and which has
SQLITE_ENABLE_LOCKING_MODE turned off.

2011-04-12 (3.7.6)

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).

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 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.

The logical database size is now stored in the database header so that
bytes can be appended to the end of the database file without corrupting
it and so that SQLite will work correctly on systems that lack support
for ftruncate().

2009-12-07 (3.6.21)

Performance optimizations targeting a specific use case from
a single high-profile user of SQLite. A 12% reduction in the number of
CPU operations is achieved (as measured by Valgrind). Actual performance
improvements in practice may vary depending on workload. Changes
include:

The ifnull() and coalesce() SQL functions are now implemented
using in-line VDBE code rather than calling external functions, so that
unused arguments need never be evaluated.

The substr() SQL function does not bother to measure the length
its entire input string if it is only computing a prefix

When new tables are created using CREATE TABLE ... AS SELECT ... the
datatype of the columns is the simplified SQLite datatype (TEXT, INT,
REAL, NUMERIC, or BLOB) instead of a copy of the original datatype from
the source table.

2008-07-16 (3.6.0 beta)

Modifications to the virtual file system interface
to support a wider range of embedded systems.
See 35to36.html for additional information.
*** Potentially incompatible change ***

All C-preprocessor macros used to control compile-time options
now begin with the prefix "SQLITE_". This may require changes to
applications that compile SQLite using their own makefiles and with
custom compile-time options, hence we mark this as a
*** Potentially incompatible change ***

The SQLITE_MUTEX_APPDEF compile-time option is no longer supported.
Alternative mutex implementations can now be added at run-time using
the sqlite3_config() interface with the SQLITE_CONFIG_MUTEX verb.
*** Potentially incompatible change ***

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, we mark that as a
*** Potentially incompatible change ***

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.

2008-01-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-12-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.)

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-10-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 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.

2007-01-22 (3.3.11)

Fix another bug in the implementation of the new
sqlite3_prepare_v2() API.
We'll get it right eventually...

Fix a bug in the IS NULL optimization that was added in version 3.3.9 -
the bug was causing incorrect results on certain LEFT JOINs that included
in the WHERE clause an IS NULL constraint for the right table of the
LEFT JOIN.

Make AreFileApisANSI() a no-op macro in WinCE since WinCE does not
support this function.

Database cache can be optionally shared between connections
in the same thread

Optional READ UNCOMMITTED isolation (instead of the default
isolation level of SERIALIZABLE) and table level locking when
database connections share a common cache.

2005-12-19 (3.2.8)

Fix an obscure bug that can cause database corruption under the
following unusual circumstances: A large INSERT or UPDATE statement which
is part of an even larger transaction fails due to a uniqueness constraint
but the containing transaction commits.

2005-12-19 (2.8.17)

Fix an obscure bug that can cause database corruption under the
following unusual circumstances: A large INSERT or UPDATE statement which
is part of an even larger transaction fails due to a uniqueness contraint
but the containing transaction commits.

2005-09-24 (3.2.7)

GROUP BY now considers NULLs to be equal again, as it should

Now compiles on Solaris and OpenBSD and other Unix variants
that lack the fdatasync() function

2005-08-21 (3.2.3)

Allow the DEFAULT value of a column to call functions that have constant
operands

Added the ANALYZE command for gathering statistics on indices and
using those statistics when picking an index in the optimizer

Remove the limit (formerly 100) on the number of terms in the
WHERE clause

The right-hand side of the IN operator can now be a list of expressions
instead of just a list of constants

Rework the optimizer so that it is able to make better use of indices

The order of tables in a join is adjusted automatically to make
better use of indices

The IN operator is now a candidate for optimization even if the left-hand
side is not the left-most term of the index. Multiple IN operators can be
used with the same index.

WHERE clause expressions using BETWEEN and OR are now candidates
for optimization

Added the "case_sensitive_like" pragma and the SQLITE_CASE_SENSITIVE_LIKE
compile-time option to set its default value to "on".

Use indices to help with GLOB expressions and LIKE expressions too
when the case_sensitive_like pragma is enabled

Added support for grave-accent quoting for compatibility with MySQL

Improved test coverage

Dozens of minor bug fixes

2005-06-12 (3.2.2)

Added the sqlite3_db_handle() API

Added the sqlite3_get_autocommit() API

Added a REGEXP operator to the parser. There is no function to back
up this operator in the standard build but users can add their own using
sqlite3_create_function()

Speed improvements and library footprint reductions.

Fix byte alignment problems on 64-bit architectures.

Many, many minor bug fixes and documentation updates.

2005-03-29 (3.2.1)

Fix a memory allocation error in the new ADD COLUMN comment.

Documentation updates

2005-03-21 (3.2.0)

Added support for ALTER TABLE ADD COLUMN.

Added support for the "T" separator in ISO-8601 date/time strings.

Improved support for Cygwin.

Numerous bug fixes and documentation updates.

2005-03-17 (3.1.6)

Fix a bug that could cause database corruption when inserting
record into tables with around 125 columns.

sqlite3_step() is now much more likely to invoke the busy handler
and less likely to return SQLITE_BUSY.

Fix memory leaks that used to occur after a malloc() failure.

2005-03-11 (3.1.5)

The ioctl on Mac OS X to control syncing to disk is F_FULLFSYNC,
not F_FULLSYNC. The previous release had it wrong.

2005-03-11 (3.1.4)

Fix a bug in autovacuum that could cause database corruption if
a CREATE UNIQUE INDEX fails because of a constraint violation.
This problem only occurs if the new autovacuum feature introduced in
version 3.1 is turned on.

The F_FULLSYNC ioctl (currently only supported on Mac OS X) is disabled
if the synchronous pragma is set to something other than "full".

2004-06-09 (2.8.14)

Fix the min() and max() optimizer so that it works when the FROM
clause consists of a subquery.

Ignore extra whitespace at the end of of "." commands in the shell.

Bundle sqlite_encode_binary() and sqlite_decode_binary() with the
library.

The TEMP_STORE and DEFAULT_TEMP_STORE pragmas now work.

Code changes to compile cleanly using OpenWatcom.

Fix VDBE stack overflow problems with INSTEAD OF triggers and
NULLs in IN operators.

Add the global variable sqlite_temp_directory which if set defines the
directory in which temporary files are stored.

sqlite_interrupt() plays well with VACUUM.

Other minor bug fixes.

2004-03-08 (2.8.13)

Refactor parts of the code in order to make the code footprint
smaller. The code is now also a little bit faster.

sqlite_exec() is now implemented as a wrapper around sqlite_compile()
and sqlite_step().

The built-in min() and max() functions now honor the difference between
NUMERIC and TEXT datatypes. Formerly, min() and max() always assumed
their arguments were of type NUMERIC.

New HH:MM:SS modifier to the built-in date/time functions.

Experimental sqlite_last_statement_changes() API added. Fixed
the last_insert_rowid() function so that it works correctly with
triggers.

Add functions prototypes for the database encryption API.

Fix several nuisance bugs.

2004-02-08 (2.8.12)

Fix a bug that will might corrupt the rollback journal if a power failure
or external program halt occurs in the middle of a COMMIT. The corrupt
journal can lead to database corruption when it is rolled back.

Reduce the size and increase the speed of various modules, especially
the virtual machine.

Allow "<expr> IN <table>" as a shorthand for
"<expr> IN (SELECT * FROM <table>".

Optimizations to the sqlite_mprintf() routine.

Make sure the MIN() and MAX() optimizations work within subqueries.

2004-01-14 (2.8.11)

Fix a bug in how the IN operator handles NULLs in subqueries. The bug
was introduced by the previous release.

2004-01-14 (2.8.10)

Fix a potential database corruption problem on Unix caused by the fact
that all POSIX advisory locks are cleared whenever you close() a file.
The work around it to embargo all close() calls while locks are
outstanding.

Performance enhancements on some corner cases of COUNT(*).

Make sure the in-memory backend response sanely if malloc() fails.

Allow sqlite_exec() to be called from within user-defined SQL
functions.

Improved accuracy of floating-point conversions using "long double".

Bug fixes in the experimental date/time functions.

2004-01-06 (2.8.9)

Fix a 32-bit integer overflow problem that could result in corrupt
indices in a database if large negative numbers (less than -2147483648)
were inserted into an indexed numeric column.

Fix a locking problem on multi-threaded Linux implementations.

Always use "." instead of "," as the decimal point even if the locale
requests ",".

Added UTC to localtime conversions to the experimental date/time
functions.

Bug fixes to date/time functions.

2003-12-18 (2.8.8)

Fix a critical bug introduced into 2.8.0 which could cause
database corruption.

Fix a problem with 3-way joins that do not use indices

The VACUUM command now works with the non-callback API

Improvements to the "PRAGMA integrity_check" command

2003-12-04 (2.8.7)

Added experimental sqlite_bind() and sqlite_reset() APIs.

If the name of the database is an empty string, open a new database
in a temporary file that is automatically deleted when the database
is closed.

Performance enhancements in the lemon-generated parser

Experimental date/time functions revised.

Disallow temporary indices on permanent tables.

Documentation updates and typo fixes

Added experimental sqlite_progress_handler() callback API

Removed support for the Oracle8 outer join syntax.

Allow GLOB and LIKE operators to work as functions.

Other minor documentation and makefile changes and bug fixes.

2003-08-22 (2.8.6)

Moved the CVS repository to www.sqlite.org

Update the NULL-handling documentation.

Experimental date/time functions added.

Bug fix: correctly evaluate a view of a view without segfaulting.

Bug fix: prevent database corruption if you dropped a
trigger that had the same name as a table.

Bug fix: allow a VACUUM (without segfaulting) on an empty
database after setting the EMPTY_RESULT_CALLBACKS pragma.

Bug fix: if an integer value will not fit in a 32-bit int, store it in
a double instead.

Bug fix: Make sure the journal file directory entry is committed to disk
before writing the database file.

2003-07-22 (2.8.5)

Make LIMIT work on a compound SELECT statement.

LIMIT 0 now shows no rows. Use LIMIT -1 to see all rows.

Correctly handle comparisons between an INTEGER PRIMARY KEY and
a floating point number.

2002-07-18 (2.6.0)

Change the format of indices to correct a design flaw the originated
with version 2.1.0. *** This is an incompatible
file format change *** When version 2.6.0 or later of the
library attempts to open a database file created by version 2.5.6 or
earlier, it will automatically and irreversibly convert the file format.
Make backup copies of older database files before opening them with
version 2.6.0 of the library.

2002-07-07 (2.5.6)

Fix more problems with rollback. Enhance the test suite to exercise
the rollback logic extensively in order to prevent any future problems.

2002-07-06 (2.5.5)

Fix a bug which could cause database corruption during a rollback.
This bugs was introduced in version 2.4.0 by the freelist
optimization of checkin [410].

Fix a bug in aggregate functions for VIEWs.

Other minor changes and enhancements.

2002-07-01 (2.5.4)

Make the "AS" keyword optional again.

The datatype of columns now appear in the 4th argument to the
callback.

Added the sqlite_open_aux_file() API, though it is still
mostly undocumented and untested.

Added additional test cases and fixed a few bugs that those
test cases found.

2002-06-25 (2.5.3)

Bug fix: Database corruption can occur due to the optimization
that was introduced in version 2.4.0 (check-in [410]). The problem
should now be fixed. The use of versions 2.4.0 through 2.5.2 is
not recommended.

2002-06-25 (2.5.2)

Added the new SQLITE_TEMP_MASTER table which records the schema
for temporary tables in the same way that SQLITE_MASTER does for
persistent tables.

Added an optimization to UNION ALL

Fixed a bug in the processing of LEFT OUTER JOIN

The LIMIT clause now works on subselects

ORDER BY works on subselects

There is a new TypeOf() function used to determine if an expression
is numeric or text.

Autoincrement now works for INSERT from a SELECT.

2002-06-19 (2.5.1)

The query optimizer now attempts to implement the ORDER BY clause
using an index. Sorting is still used if not suitable index is
available.

2002-06-17 (2.5.0)

Added support for row triggers.

Added SQL-92 compliant handling of NULLs.

Add support for the full SQL-92 join syntax and LEFT OUTER JOINs.

Double-quoted strings interpreted as column names not text literals.

Parse (but do not implement) foreign keys.

Performance improvements in the parser, pager, and WHERE clause code
generator.

Make the LIMIT clause work on subqueries. (ORDER BY still does not
work, though.)

Added the "%Q" expansion to sqlite_*_printf().

Bug fixes too numerous to mention (see the change log).

2002-05-10 (2.4.12)

Added logic to detect when the library API routines are called out
of sequence.

2002-05-08 (2.4.11)

Bug fix: Column names in the result set were not being generated
correctly for some (rather complex) VIEWs. This could cause a
segfault under certain circumstances.

2002-05-03 (2.4.10)

Bug fix: Generate correct column headers when a compound SELECT is used
as a subquery.

Added the sqlite_encode_binary() and sqlite_decode_binary() functions to
the source tree. But they are not yet linked into the library.

Documentation updates.

Export the sqlite_changes() function from Windows DLLs.

Bug fix: Do not attempt the subquery flattening optimization on queries
that lack a FROM clause. To do so causes a segfault.

2002-04-22 (2.4.9)

Fix a bug that was causing the precompiled binary of SQLITE.EXE to
report "out of memory" under Windows 98.

2002-04-20 (2.4.8)

Make sure VIEWs are created after their corresponding TABLEs in the
output of the .dump command in the shell.

Speed improvements: Do not do synchronous updates on TEMP tables.

Many improvements and enhancements to the shell.

Make the GLOB and LIKE operators functions that can be overridden
by a programmer. This allows, for example, the LIKE operator to
be changed to be case sensitive.

2002-04-12 (2.4.7)

Add the ability to put TABLE.* in the column list of a
SELECT statement.

Permit SELECT statements without a FROM clause.

Added the last_insert_rowid() SQL function.

Do not count rows where the IGNORE conflict resolution occurs in
the row count.

Make sure functions expressions in the VALUES clause of an INSERT
are correct.

Added the sqlite_changes() API function to return the number
of row that changed in the most recent operation.

2002-04-02 (2.4.6)

Bug fix: Correctly handle terms in the WHERE clause of a join that
do not contain a comparison operator.

2002-04-02 (2.4.5)

Bug fix: Correctly handle functions that appear in the WHERE clause
of a join.

When the PRAGMA vdbe_trace=ON is set, correctly print the P3 operand
value when it is a pointer to a structure rather than a pointer to
a string.

When inserting an explicit NULL into an INTEGER PRIMARY KEY, convert
the NULL value into a unique key automatically.

2002-03-30 (2.4.4)

Allow "VIEW" to be a column name

Added support for CASE expressions (patch from Dan Kennedy)

Added RPMS to the delivery (patches from Doug Henry)

Fix typos in the documentation

Cut over configuration management to a new CVS repository with
its own CVSTrac bug tracking system.

2002-03-23 (2.4.3)

Fix a bug in SELECT that occurs when a compound SELECT is used as a
subquery in the FROM of a SELECT.

The sqlite_get_table() function now returns an error if you
give it two or more SELECTs that return different numbers of columns.

2002-03-20 (2.4.2)

Bug fix: Fix an assertion failure that occurred when ROWID was a column
in a SELECT statement on a view.

Bug fix: Fix an uninitialized variable in the VDBE that would could an
assert failure.

Make the os.h header file more robust in detecting when the compile is
for Windows and when it is for Unix.

2002-03-13 (2.4.1)

Using an unnamed subquery in a FROM clause would cause a segfault.

The parser now insists on seeing a semicolon or the end of input before
executing a statement. This avoids an accidental disaster if the
WHERE keyword is misspelled in an UPDATE or DELETE statement.

2002-03-11 (2.4.0)

Change the name of the sanity_check PRAGMA to integrity_check
and make it available in all compiles.

SELECT min() or max() of an indexed column with no WHERE or GROUP BY
clause is handled as a special case which avoids a complete table scan.

Automatically generated ROWIDs are now sequential.

Do not allow dot-commands of the command-line shell to occur in the
middle of a real SQL command.

Modifications to the "lemon" parser generator so that the parser tables
are 4 times smaller.

Added support for user-defined functions implemented in C.

Added support for new functions: coalesce(), lower(),
upper(), and random()

Added support for VIEWs.

Added the subquery flattening optimizer.

Modified the B-Tree and Pager modules so that disk pages that do not
contain real data (free pages) are not journaled and are not
written from memory back to the disk when they change. This does not
impact database integrity, since the
pages contain no real data, but it does make large INSERT operations
about 2.5 times faster and large DELETEs about 5 times faster.

Made the CACHE_SIZE pragma persistent

Added the SYNCHRONOUS pragma

Fixed a bug that was causing updates to fail inside of transactions when
the database contained a temporary table.

2002-02-19 (2.3.3)

Allow identifiers to be quoted in square brackets, for compatibility
with MS-Access.

Added support for sub-queries in the FROM clause of a SELECT.

More efficient implementation of sqliteFileExists() under Windows.
(by Joel Luscy)

The VALUES clause of an INSERT can now contain expressions, including
scalar SELECT clauses.

Added support for CREATE TABLE AS SELECT

Bug fix: Creating and dropping a table all within a single
transaction was not working.

2002-02-14 (2.3.2)

Bug fix: There was an incorrect assert() in pager.c. The real code was
all correct (as far as is known) so everything should work OK if you
compile with -DNDEBUG=1. When asserts are not disabled, there
could be a fault.

2002-02-13 (2.3.1)

Bug fix: An assertion was failing if "PRAGMA full_column_names=ON;" was
set and you did a query that used a rowid, like this:
"SELECT rowid, * FROM ...".

2002-02-03 (2.3.0)

Fix a serious bug in the INSERT command which was causing data to go
into the wrong columns if the data source was a SELECT and the INSERT
clauses specified its columns in some order other than the default.

Added the ability to resolve constraint conflicts is ways other than
an abort and rollback. See the documentation on the "ON CONFLICT"
clause for details.

Temporary files are now automatically deleted by the operating system
when closed. There are no more dangling temporary files on a program
crash. (If the OS crashes, fsck will delete the file after reboot
under Unix. I do not know what happens under Windows.)

NOT NULL constraints are honored.

The COPY command puts NULLs in columns whose data is '\N'.

In the COPY command, backslash can now be used to escape a newline.

Added the SANITY_CHECK pragma.

2002-01-28 (2.2.5)

Important bug fix: the IN operator was not working if either the
left-hand or right-hand side was derived from an INTEGER PRIMARY KEY.

Do not escape the backslash '\' character in the output of the
sqlite command-line access program.

2002-01-22 (2.2.4)

The label to the right of an AS in the column list of a SELECT can now
be used as part of an expression in the WHERE, ORDER BY, GROUP BY, and/or
HAVING clauses.

Fix a bug in the -separator command-line option to the sqlite
command.

Fix a problem with the sort order when comparing upper-case strings against
characters greater than 'Z' but less than 'a'.

Report an error if an ORDER BY or GROUP BY expression is constant.

2002-01-16 (2.2.3)

Fix warning messages in VC++ 7.0. (Patches from nicolas352001)

Make the library thread-safe. (The code is there and appears to work
but has not been stressed.)

Added the new sqlite_last_insert_rowid() API function.

2002-01-14 (2.2.2)

Bug fix: An assertion was failing when a temporary table with an index
had the same name as a permanent table created by a separate process.

Bug fix: Updates to tables containing an INTEGER PRIMARY KEY and an
index could fail.

2002-01-09 (2.2.1)

Bug fix: An attempt to delete a single row of a table with a WHERE
clause of "ROWID=x" when no such rowid exists was causing an error.

Bug fix: Passing in a NULL as the 3rd parameter to sqlite_open()
would sometimes cause a coredump.

Bug fix: DROP TABLE followed by a CREATE TABLE with the same name all
within a single transaction was causing a coredump.

Makefile updates from A. Rottmann

2001-12-22 (2.2.0)

Columns of type INTEGER PRIMARY KEY are actually used as the primary
key in underlying B-Tree representation of the table.

Several obscure, unrelated bugs were found and fixed while
implemented the integer primary key change of the previous bullet.

Added the ability to specify "*" as part of a larger column list in
the result section of a SELECT statement. For example:
"SELECT rowid, * FROM table1;".

Updates to comments and documentation.

2001-12-15 (2.1.7)

Fix a bug in CREATE TEMPORARY TABLE which was causing the
table to be initially allocated in the main database file instead
of in the separate temporary file. This bug could cause the library
to suffer an assertion failure and it could cause "page leaks" in the
main database file.

Fix a bug in the b-tree subsystem that could sometimes cause the first
row of a table to be repeated during a database scan.

2001-12-14 (2.1.6)

Fix the locking mechanism yet again to prevent
sqlite_exec() from returning SQLITE_PROTOCOL
unnecessarily. This time the bug was a race condition in
the locking code. This change affects both POSIX and Windows users.

2001-12-06 (2.1.5)

Fix for another problem (unrelated to the one fixed in 2.1.4)
that sometimes causes sqlite_exec() to return SQLITE_PROTOCOL
unnecessarily. This time the bug was
in the POSIX locking code and should not effect Windows users.

2001-12-05 (2.1.4)

Sometimes sqlite_exec() would return SQLITE_PROTOCOL when it
should have returned SQLITE_BUSY.

The fix to the previous bug uncovered a deadlock which was also
fixed.

Add the ability to put a single .command in the second argument
of the sqlite shell

Updates to the FAQ

2001-11-24 (2.1.3)

Fix the behavior of comparison operators
(ex: "&lt", "==", etc.)
so that they are consistent with the order of entries in an index.

Correct handling of integers in SQL expressions that are larger than
what can be represented by the machine integer.

2001-11-23 (2.1.2)

Changes to support 64-bit architectures.

Fix a bug in the locking protocol.

Fix a bug that could (rarely) cause the database to become
unreadable after a DROP TABLE due to corruption to the SQLITE_MASTER
table.

Change the code so that version 2.1.1 databases that were rendered
unreadable by the above bug can be read by this version of
the library even though the SQLITE_MASTER table is (slightly)
corrupted.

2001-11-13 (2.1.1)

Bug fix: Sometimes arbitrary strings were passed to the callback
function when the actual value of a column was NULL.

2001-11-12 (2.1.0)

Change the format of data records so that records up to 16MB in size
can be stored.

Change the format of indices to allow for better query optimization.

Implement the "LIMIT ... OFFSET ..." clause on SELECT statements.

2001-11-03 (2.0.8)

Made selected parameters in API functions const. This should
be fully backwards compatible.

Documentation updates

Simplify the design of the VDBE by restricting the number of sorters
and lists to 1.
In practice, no more than one sorter and one list was ever used anyhow.

2001-10-22 (2.0.7)

Any UTF-8 character or ISO8859 character can be used as part of
an identifier.

Patches from Christian Werner to improve ODBC compatibility and to
fix a bug in the round() function.

Plug some memory leaks that use to occur if malloc() failed.
We have been and continue to be memory leak free as long as
malloc() works.

Changes to some test scripts so that they work on Windows in
addition to Unix.

2001-10-09 (2.0.2)

Added the FULL_COLUMN_NAMES pragma. When set to "ON", the names of
columns are reported back as TABLE.COLUMN instead of just COLUMN.

Added the TABLE_INFO() and INDEX_INFO() pragmas to help support the
ODBC interface.

Added support for TEMPORARY tables and indices.

2001-10-02 (2.0.1)

Remove some C++ style comments from btree.c so that it will compile
using compilers other than gcc.

The ".dump" output from the shell does not work if there are embedded
newlines anywhere in the data. This is an old bug that was carried
forward from version 1.0. To fix it, the ".dump" output no longer
uses the COPY command. It instead generates INSERT statements.

Extend the expression syntax to support "expr NOT NULL" (with a
space between the "NOT" and the "NULL") in addition to "expr NOTNULL"
(with no space).

2001-09-28 (2.0.0)

Automatically build binaries for Linux and Windows and put them on
the website.

2001-09-28 (2.0-alpha-4)

Incorporate makefile patches form A. Rottmann to use LIBTOOL

2001-09-27 (2.0-alpha-3)

SQLite now honors the UNIQUE keyword in CREATE UNIQUE INDEX. Primary
keys are required to be unique.

File format changed back to what it was for alpha-1

Fixes to the rollback and locking behavior

2001-09-20 (2.0-alpha-2)

Initial release of version 2.0. The idea of renaming the library
to "SQLus" was abandoned in favor of keeping the "SQLite" name and
bumping the major version number.

The pager and btree subsystems added back. They are now the only
available backend.

The Dbbe abstraction and the GDBM and memory drivers were removed.

Copyright on all code was disclaimed. The library is now in the
public domain.

2001-07-23 (1.0.32)

Pager and btree subsystems removed. These will be used in a follow-on
SQL server library named "SQLus".

Add the ability to use quoted strings as table and column names in
expressions.

2001-04-15 (1.0.31)

Pager subsystem added but not yet used.

More robust handling of out-of-memory errors.

New tests added to the test suite.

2001-04-06 (1.0.30)

Remove the sqlite_encoding TCL variable that was introduced
in the previous version.

Add options -encoding and -tcl-uses-utf to the
sqlite TCL command.

Add tests to make sure that tclsqlite was compiled using Tcl header
files and libraries that match.

2001-04-05 (1.0.29)

The library now assumes data is stored as UTF-8 if the --enable-utf8
option is given to configure. The default behavior is to assume
iso8859-x, as it has always done. This only makes a difference for
LIKE and GLOB operators and the LENGTH and SUBSTR functions.

If the library is not configured for UTF-8 and the Tcl library
is one of the newer ones that uses UTF-8 internally,
then a conversion from UTF-8 to iso8859 and
back again is done inside the TCL interface.

2001-04-04 (1.0.28)

Added limited support for transactions. At this point, transactions
will do table locking on the GDBM backend. There is no support (yet)
for rollback or atomic commit.

Added special column names ROWID, OID, and _ROWID_ that refer to the
unique random integer key associated with every row of every table.

Additional tests added to the regression suite to cover the new ROWID
feature and the TCL interface bugs mentioned below.

Changes to the "lemon" parser generator to help it work better when
compiled using MSVC.

Bug fixes in the TCL interface identified by Oleg Oleinick.

2001-03-20 (1.0.27)

When doing DELETE and UPDATE, the library used to write the record
numbers of records to be deleted or updated into a temporary file.
This is changed so that the record numbers are held in memory.

The DELETE command without a WHILE clause just removes the database
files from the disk, rather than going through and deleting record
by record.

2001-03-20 (1.0.26)

A serious bug fixed on Windows. Windows users should upgrade.
No impact to Unix.

2001-03-15 (1.0.25)

Modify the test scripts to identify tests that depend on system
load and processor speed and
to warn the user that a failure of one of those (rare) tests does
not necessarily mean the library is malfunctioning. No changes to
code.

2001-03-14 (1.0.24)

Fix a bug which was causing
the UPDATE command to fail on systems where "malloc(0)" returns
NULL. The problem does not appear on Windows, Linux, or HPUX but does
cause the library to fail on QNX.

2001-02-20 (1.0.23)

An unrelated (and minor) bug from Mark Muranwski fixed. The algorithm
for figuring out where to put temporary files for a "memory:" database
was not working quite right.

2001-02-19 (1.0.22)

The previous fix was not quite right. This one seems to work better.

2001-02-19 (1.0.21)

The UPDATE statement was not working when the WHERE clause contained
some terms that could be satisfied using indices and other terms that
could not. Fixed.

2001-02-11 (1.0.20)

Merge development changes into the main trunk. Future work toward
using a BTree file structure will use a separate CVS source tree. This
CVS tree will continue to support the GDBM version of SQLite only.

2001-02-06 (1.0.19)

Fix a strange (but valid) C declaration that was causing problems
for QNX. No logical changes.

2001-01-04 (1.0.18)

Print the offending SQL statement when an error occurs.

Do not require commas between constraints in CREATE TABLE statements.

Added the "-echo" option to the shell.

Changes to comments.

2000-12-10 (1.0.17)

Rewrote sqlite_complete() to make it faster.

Minor tweaks to other code to make it run a little faster.

Added new tests for sqlite_complete() and for memory leaks.

2000-11-28 (1.0.16)

Documentation updates. Mostly fixing of typos and spelling errors.

2000-10-23 (1.0.15)

Documentation updates

Some sanity checking code was removed from the inner loop of vdbe.c
to help the library to run a little faster. The code is only
removed if you compile with -DNDEBUG.

2000-10-19 (1.0.14)

Added a "memory:" backend driver that stores its database in an
in-memory hash table.

2000-10-19 (1.0.13)

Break out the GDBM driver into a separate file in anticipation
to added new drivers.

Allow the name of a database to be prefixed by the driver type.
For now, the only driver type is "gdbm:".

2000-10-17 (1.0.12)

Fixed an off-by-one error that was causing a coredump in
the '%q' format directive of the new
sqlite_..._printf() routines.

Added the sqlite_interrupt() interface.

In the shell, sqlite_interrupt() is invoked when the
user presses Control-C

Fixed some instances where sqlite_exec() was
returning the wrong error code.

2000-10-11 (1.0.10)

Added notes on how to compile for Windows95/98.

Removed a few variables that were not being used. Etc.

2000-10-09 (1.0.9)

Added the sqlite_..._printf() interface routines.

Modified the sqlite shell program to use the new interface
routines.

Modified the sqlite shell program to print the schema for
the built-in SQLITE_MASTER table, if explicitly requested.

2000-09-30 (1.0.8)

Begin writing documentation on the TCL interface.

2000-09-29 (Not Released)

Added the sqlite_get_table() API

Updated the documentation for due to the above change.

Modified the sqlite shell to make use of the new
sqlite_get_table() API in order to print a list of tables
in multiple columns, similar to the way "ls" prints filenames.

Modified the sqlite shell to print a semicolon at the
end of each CREATE statement in the output of the ".schema" command.

2000-09-21 (Not Released)

Change the tclsqlite "eval" method to return a list of results if
no callback script is specified.

Change tclsqlite.c to use the Tcl_Obj interface

Add tclsqlite.c to the libsqlite.a library

2000-09-14 (1.0.5)

Changed the print format for floating point values from "%g" to "%.15g".

Changed the comparison function so that numbers in exponential notation
(ex: 1.234e+05) sort in numerical order.

2000-08-28 (1.0.4)

Added functions length() and substr().

Fix a bug in the sqlite shell program that was causing
a coredump when the output mode was "column" and the first row
of data contained a NULL.

2000-08-22 (1.0.3)

In the sqlite shell, print the "Database opened READ ONLY" message
to stderr instead of stdout.

In the sqlite shell, now print the version number on initial startup.

Add the sqlite_version[] string constant to the library

Makefile updates

Bug fix: incorrect VDBE code was being generated for the following
circumstance: a query on an indexed table containing a WHERE clause with
an IN operator that had a subquery on its right-hand side.

2000-08-18 (1.0.1)

Fix a bug in the configure script.

Minor revisions to the website.

2000-08-17 (1.0)

Change the sqlite program so that it can read
databases for which it lacks write permission. (It used to
refuse all access if it could not write.)

2000-08-09

Treat carriage returns as white space.

2000-08-08

Added pattern matching to the ".table" command in the "sqlite"
command shell.

2000-08-04

Documentation updates

Added "busy" and "timeout" methods to the Tcl interface

2000-08-03

File format version number was being stored in sqlite_master.tcl
multiple times. This was harmless, but unnecessary. It is now fixed.

2000-08-02

The file format for indices was changed slightly in order to work
around an inefficiency that can sometimes come up with GDBM when
there are large indices having many entries with the same key.
** Incompatible Change **

2000-08-01

The parser's stack was overflowing on a very long UPDATE statement.
This is now fixed.

2000-07-29

2000-07-28

2000-06-23

2000-06-21

Clean up comments and variable names. Changes to documentation.
No functional changes to the code.

2000-06-19

Column names in UPDATE statements were case sensitive.
This mistake has now been fixed.

2000-06-18

Added the concatenate string operator (||)

2000-06-12

Added the fcnt() function to the SQL interpreter. The fcnt() function
returns the number of database "Fetch" operations that have occurred.
This function is designed for use in test scripts to verify that
queries are efficient and appropriately optimized. Fcnt() has no other
useful purpose, as far as I know.

Added a bunch more tests that take advantage of the new fcnt() function.
The new tests did not uncover any new problems.

NULL values are now reported to the callback as a NULL pointer
rather than an empty string.

2000-06-03

Added support for default values on columns of a table.

Improved test coverage. Fixed a few obscure bugs found by the
improved tests.

2000-06-02

All database files to be modified by an UPDATE, INSERT or DELETE are
now locked before any changes are made to any files.
This makes it safe (I think) to access
the same database simultaneously from multiple processes.

The code appears stable so we are now calling it "beta".

2000-06-01

Better support for file locking so that two or more processes
(or threads)
can access the same database simultaneously. More work needed in
this area, though.

2000-05-31

Added support for aggregate functions (Ex: COUNT(*), MIN(...))
to the SELECT statement.

Added support for SELECT DISTINCT ...

2000-05-30

Added the LIKE operator.

Added a GLOB operator: similar to LIKE
but it uses Unix shell globbing wildcards instead of the '%'
and '_' wildcards of SQL.

Added the COPY command patterned after
PostgreSQL so that SQLite
can now read the output of the pg_dump database dump utility
of PostgreSQL.

Added a VACUUM command that calls the
gdbm_reorganize() function on the underlying database
files.