DISQLite3 implements a self-contained, embeddable, zero-configuration SQL database engine.

Here are some key features of "DISQLite3":

· ACID transactions, even after system crashes and power failures.
· Zero-configuration – no setup or administration needed.
· Implements most of SQL-92.
· A complete database is stored in a single disk file.
· Supports terabyte-sized databases and gigabyte-sized strings and blobs. Self-contained: no external dependencies, no DLLs.
· Small footprint: less than 300 KB code space only.
· Full Text Search with customizable tokenizer and prefix matching.
· Database AES encryption with SHA256 key generator.
· Db.pas is not required, which allows DISQLite3 to compile with all flavours of Delphi, including Delphi Standard and Delphi Personal.
· Faster than popular database engines for most common operations.
· Simple, easy to use API.
· Database files created with DISQLite3 can also be accessed by Linux and MacOS using the SQLite3 libraries.


DISQLite3 will provide a comprehensive list of functions and procedures to manage database records with ease and efficiency. It includes the full SQLite3 functionality, plus a number of Delphi specific extras:
· AnsiString, WideString, and Variant support.
· Database and Statement wrapper classes.
· TDataSet support.
· TStream support for BLOBs.
· Growing number of Delphi example projects.

DISQLite3 Pro is required for commercial use and may be purchased online. It adds functionality usually desired by advanced users. This includes SQL triggers and views, arbitrary encryption passwords, user-defined SQL functions, and more. Since DISQLite3 Pro is fully compatible to the Personal edition, it is possible to upgrade existing projects without any code changes.

Requirements:

· Compilers D4, D5, D6, C6, D7, D2005 Win32, D2006 Win32, D2007 Win32

What's New in This Release: [ read full changelog ]

Bugs fixed in this version:
Problems that might cause incorrect query results:
· Queries that have a WHERE clause of the form (x AND y) OR z where x and z come from one table of a join and y comes from a different table.
· Queries where the use of the CAST operator in the WHERE clause could lead to incorrect results if the column being cast to a new datatype is also used in the same WHERE clause without being cast.
· Expressions with different COLLATIONs could compare equal and lead to wrong query results.
· When reusing an instance of TDISQLite3Database, the internal transaction counter was not reset when opening another database so its InTransaction property could return wrong results. Fixed.
· Other minor bug fixes and performance enhancements, especially for the FTS3 full text search.