GPE Database Schemes

Some collection of SQL tables and other data structures used in GPE. Usually there is no need to access this data directly, there are libraries to access each of the databases through an abstract API.

GPE-Contacts

GPE-Contacts currently uses three tables:

1: contacts_config

create table contacts_config (id INTEGER PRIMARY KEY, cgroup INTEGER NOT NULL, cidentifier TEXT NOT NULL, cvalue TEXT)

2: contacts_urn

create table contacts_urn (urn INTEGER PRIMARY KEY, name TEXT, family_name TEXT, company TEXT)

3: contacts

create table contacts (urn INTEGER NOT NULL, tag TEXT NOT NULL, value TEXT NOT NULL)

To access GPE Contacts data you can use the libcontacts database library.

The location of the database in filesystem is ~/.gpe/contacts.

GPE-Todo

GPE-Todo currently uses three tables:

1: todo

• create table todo (uid INTEGER NOT NULL, tag TEXT NOT NULL, value TEXT)

2: todo-urn

• create table todo_urn (uid INTEGER PRIMARY KEY)

3: todo_dbinfo

• create table todo_dbinfo (version integer NOT NULL)

Access to GPE Todo data is provided by the libtododb API.

The location of the database in filesystem is ~/.gpe/todo.

GPE-Calendar

The calendar data for GPE-Calendar is stored in these two tables:

1: calendar

• create table calendar (uid integer NOT NULL, tag text, value text)

2: events

• create table events (uid INTEGER PRIMARY KEY, start DATE, duration INTEGER, recur INTEGER, rend DATE, alarm INTEGER, calendar INTEGER, eventid STRING, rcount INTEGER, rincrement INTEGER, modified DATE, byday STRING, rexceptions STRING);

create index events_enumerate_index on events (start, duration, rend, alarm)

3: calendars

• create table calendars (title TEXT, description TEXT, url TEXT, username TEXT, password TEXT, parent INTEGER, hidden INTEGER, has_color INTEGER, red INTEGER, green INTEGER, blue INTEGER, mode INTEGER, sync_interval INTEGER, last_pull INTEGER, last_push INTEGER, last_modified)

Access to GPE-Calendar data is provided by the libeventdb API.

The location of the database in filesystem is ~/.gpe/calendar.

PIM Categories

The categories are shared within all GPE PIM applications and stored in one single table:

categories

• create table category (id INTEGER PRIMARY KEY, description TEXT, colour TEXT)

Access to PIM category data is provided by the libgpepimc API.

The location of the database in filesystem is ~/.gpe/categories.