bugfix:
That bug might possibly cause database corruption if a large
INSERT or UPDATE statement within a multi-statement transaction fails
due to a uniqueness constraint but the containing transaction commits.
2005 February 15 (2.8.16)
* Fix a bug that can lead to database corruption if there are two open connections
to the same database and one connection does a VACUUM and the second makes some
change to the database.
* Correctly handle quoted names in CREATE INDEX statements.
* Fix a naming conflict between sqlite.h and sqlite3.h.
* Avoid excess heap usage when copying expressions.
* Other minor bug fixes.
FreeBSD 4 portability hint from Michal Pasternak.
Some of the changes since 2.8.5 include:
* Refactor parts of the code in order to make the code footprint
smaller. The code is now also a little bit faster.
* The built-in min() and max() functions now honor the difference
between NUMERIC and TEXT datatypes.
* New HH:MM:SS modifier to the built-in date/time functions.
* Add function prototypes for the database encryption API.
* Fix a bug that might corrupt the rollback journal if a power failure or
external program halt occurs in the middle of a COMMIT.
* Reduce the size and increase the speed of various modules.
* Fix a potential database corruption problem on Unix.
* 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 a indexed numeric column.
* Fix a locking problem on multi-threaded Linux implementations.
* Fix a critical bug introduced in 2.8.0 which could cause database corruption.
* The VACUUM command now works with the non-callback API
* 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
* Documentation updates and typo fixes
* Removed support for the Oracle8 outer join syntax.
* Allow GLOB and LIKE operators to work as functions.
* Make sure the journal file directory entry is committed to disk before
writing the database file.
2003 June 4 (2.8.3)
- Fix a problem that will corrupt the indices on a table if you
do an INSERT OR REPLACE or an UPDATE OR REPLACE on a table that
contains an INTEGER PRIMARY KEY plus one or more indices.
- Add the ability for INSERT and UPDATE statements to refer to
the "rowid" (or "_rowid_" or "oid") columns.
- Other important bug fixes
2003 May 17 (2.8.2)
- Fix a problem that will corrupt the database file if you drop a
table from the main database that has a TEMP index.
2003 May 16 (2.8.1)
- Reactivated the VACUUM command that reclaims unused disk space
in a database file.
- Added the ATTACH and DETACH commands to allow interacting with
multiple database files at the same time.
- Added support for TEMP triggers and indices.
- Added support for in-memory databases.
- Removed the experimental sqlite_open_aux_file(). Its function
is subsumed in the new ATTACH command.
- The precedence order for ON CONFLICT clauses was changed so
that ON CONFLICT clauses on BEGIN statements have a higher
precedence than ON CONFLICT clauses on constraints.
- Many, many bug fixes and compatibility enhancements.
bugs removal, fixing the behaviour of comparison operators 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 and locking protocol fixes.
The author also incorporated my suggestions after the messy LP64 patches I
made; its now a lot more clean allthough there are still a few warnings but
they are checked and OK.
less invasive as posible without rewriting stuff.
The main problems were the assumption that a pointer and an int had the
same size. Also there were strange casts near calculations that were not
nessisary.
SQLite is a C library that implements an SQL database engine. Programs
that link with the SQLite library can have SQL database access without
running a separate RDBMS process. The distribution comes with a standalone
command-line access program (sqlite) that can be used to administer an
SQLite database and which serves as an example of how to use the SQLite
library.
SQLite is not a client library used to connect to a big database server.
SQLite is the server. The SQLite library reads and writes directly to and
from the database files on disk.
