UltraLite Database User's Guide
UltraLite Databases
On most platforms, UltraLite databases are held in files. On the Palm OS the database can also be held in the Palm persistent store.
UltraLite database files contain tables and indexes that represent the data. They also hold supplementary information to provide transaction processing features. For more information, see How UltraLite tracks row states.
Each database has a well-defined collation sequence (character set and sort order). The collation sequence is defined when the database is created. For more information, see Character sets in UltraLite.
Most relational database systems include a special set of tables called the system tables, or catalog. These tables hold the database schema, or metadata: they hold the definitions of all the other tables and objects in the database.
UltraLite does not store its database schema in a set of system tables. Instead, the schema is held in the database file in a compact manner. The schema definition is built into the database file in one of the following ways:
If you are using an UltraLite component, the schema definition is held in a separate file called a schema file. The schema file is specified in a connection parameter, and is applied to the database on the first connection attempt.
You can upgrade the schema of your database by supplying a new schema file and applying it to the existing database.
For more information, see The UltraLite Schema Painter.
If you are using a static UltraLite interface, the schema definition is built into the application when the database code is generated from the reference database.
For more information, see The static UltraLite development process, and The UltraLite generator.
UltraLite database files
UltraLite database characteristics
Altering the schema of UltraLite databases
Upgrading UltraLite software