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