UltraLite Database User's Guide
UltraLite databases are held in a single file (or, in the case of Palm OS, in the Palm persistent store). The database file contains tables, indexes, and also contains additional information required for synchronization.
Every database contains a schema: information about the tables, indexes, and so on that make up the database. This metadata includes column names and data types, primary and foreign key definitions, and so on. Most relational databases store the schema in a special set of tables called the system tables, or catalog. UltraLite stores its schema in a more compact form.
To create an UltraLite database, you create an UltraLite schema externally, separately from the database itself.
If you are developing applications using an UltraLite component, you create the schema in a schema file. You then apply the schema to an UltraLite database file.
If you are developing applications using a static interface, you create the schema in a reference database; when you generate your application code from the reference database, the schema is added to the application itself.
For more information, see Creating UltraLite schema files.
It is common not to deploy UltraLite database files with your application, but instead to let UltraLite create the database file and to use synchronization to fill up the database with the appropriate data.
UltraLite component applications require that you deploy a database schema file. You can write your application so that it creates a database file on the first connection attempt, and applies the schema file to this database file. Sample code is provided in the tutorials for each programming interface.
UltraLite static interface applications contain a database schema definition in the generated code. They automatically create a database and apply the schema on the first connection attempt.
For more information, see Creating UltraLite databases.
You can alter the schema of an UltraLite database by applying a new schema to the database file. As with the original schema, a new schema may be held in a schema file (UltraLite components) or in a new version of the application (static interfaces).
If you are using an UltraLite component, you can also alter the schema of an UltraLite database by executing SQL statements that modify tables and indexes (data definition statements).
For more information, see Upgrading UltraLite database schemas.
For an introduction to UltraLite database features, see UltraLite database features.
Creating UltraLite schema files
Creating UltraLite databases
Creating UltraLite database files
SQL Anywhere Studio 9.0.2
Copyright © 1989–2004 Sybase, Inc. Portions copyright © 2001–2004 iAnywhere Solutions, Inc. All rights reserved.