Chapter 2. Sqlite Specific Issues
Prev |  | Next

## Chapter 2. Sqlite Specific Issues

The text in this chapter is take from Sqlite home page. Read more documentation there for deeper understanding of Sqlite features.

SQLite is a small C library that implements a self-contained, embeddable, zero-configuration SQL database engine.

### Caution

It's strongly recommended to read and understand the Sqlite documentation. Sqlite can be confusing for a programmer from the world of the real databases (like Postgresql, Oracle, MS SQL Server etc.).

Features include:

- Transactions are atomic, consistent, isolated, and durable (ACID) even after system crashes and power failures.

- Zero-configuration - no setup or administration needed.

- Implements most of SQL92. (Features not supported)

- A complete database is stored in a single disk file.

- Database files can be freely shared between machines with different byte orders.

- Supports databases up to 2 tebibytes in size.

- Strings and BLOBs up to 2 gibibytes in size.

- Small code footprint: less than 250KiB fully configured or less than 150KiB with optional features omitted.

- Faster than popular client/server database engines for most common operations.

- Simple, easy to use API.

- TCL bindings included. Bindings for many other languages available separately.

- Well-commented source code with over 95% test coverage.

- Self-contained: no external dependencies.

- Sources are in the public domain. Use for any purpose.

Sqlite specific properties affect Sqliteman feature set. E.g. Sqlite does not support foreign keys so there is a dedicated dialog for FK triggers creating.

Prev |  | Next
Chapter 1. Introduction | Contents | Chapter 3. Start the Application