PersonalDB - Schema

Schema

PersonalDB defines a number of standard schema. Each schema describes a number of tables that will in the database, along with some SQL triggers to enforce data integrity.

The following list is not necessarily complete, and only represents those schema that are part of the core PersonalDB standard. Other schema can be published.

All of the tables used in the standard schema start with the same three fields, id, created_time, and modified_time. The field id is defined as integer fields, and is used as the primary key for these tables. Further, SQL triggers are added to the tables that raise an error if non-integer values are assigned to these tables. The fields created_time and modified_time are also defined as integer fields. Triggers are added to the tables that update these fields with timestamps.

The standard schema are heavily influenced by the record structures used by the PalmOS for its PIM capabilities.

Appointment

Contacts

Favorite URLs

Memos

Notices

Todo Items

Extending Schema

The tables in the standard schema should not be modified. Adding additional fields is discouraged. However, there are cases where certain applications will want to extend a standard schema. This section describes how that should be done.

If additional fields are desired, the best solution is to create a new table. One can, if desired, add triggers to the original data tables to automatically create and delete records in the new table.

Todo: Expand and provide example.