Calendar database
(reformat page, condense information to one table per database table) |
(→Birthdays) |
||
| Line 18: | Line 18: | ||
==== [[#toc|Birthdays]] ==== | ==== [[#toc|Birthdays]] ==== | ||
| - | = | + | {| class="wikitable" |
| - | + | |+ Birthdays table | |
| - | + | |- | |
| + | ! Field !! Type !! Description | ||
| + | |- | ||
| + | | Id || integer || primary key | ||
| + | |- | ||
| + | | DayMonth || integer || Day and month as a combined integer. Calculated as: month*100+day (day with a leading zero). 1102 means November 2 | ||
| + | |- | ||
| + | | Year || integer || Year as a number. | ||
| + | |} | ||
==== [[#toc|Calendars]] ==== | ==== [[#toc|Calendars]] ==== | ||
Revision as of 18:03, 18 September 2011
The Maemo 5 calendar database can be found in /home/user/.calendar/calendardb. The goal of this article is to provide enough information on the calendar database in order to implement mass modifying/adding/deleting events verifying some criterias (string match in title, locations, comments for example). It could be easy then to write a small shell script using zenity and sqlite3 to perform this tasks.
If you want to help editing this article and writing useful informations on fields or new scripts, feel free to copy your own database on your computer and analyze it with some tools like "SQLite Database Browser" (Linux/Debian). The datatypes are those listed in the SQLite documentation.
Contents |
Structure
Tables & fields
ALARM
Id
Trigger
Repeat
Duration
Action
CookieId
Attach
Birthdays
| Field | Type | Description |
|---|---|---|
| Id | integer | primary key |
| DayMonth | integer | Day and month as a combined integer. Calculated as: month*100+day (day with a leading zero). 1102 means November 2 |
| Year | integer | Year as a number. |
Calendars
| Field | Type | Description |
|---|---|---|
| CalendarId | integer | primary key |
| Name | text | name of the calendar |
| Colour | integer | 0 = dark blue, 1 = green, 2 = dark pink, 3 = orange, 4 = purple, 5 = yellow, 6 = white, 7 = light blue, 8 = light pink, 9 = yellow-green |
| isVisible | integer | 0 = not visible, 1 = visible |
| isReadonly | integer | 0 = writeable, 1 = not writeable |
| CalendarType | integer | 0 = local, 1 = intelligent, 2 = ?, 3 = private, 4 = synchronized |
| CalendarTune | text | Path to the calendar alarm sound. Default path: /usr/share/sounds/ui-calendar_alarm_default.aac
|
| CalendarVersion | ||
| CalendarProfile |
ComponentDetails
Id
ComponentType
Class
Geo
Priority
DateStamp
Sequence
Transparency
Uid
Url
Attach
Category
Comment
Contact
Related
Resources
Percent
Completed
Components
| Field | Type | Description |
|---|---|---|
| Id | integer | primary key |
| CalendarId | integer | association with the corresponding calender |
| ComponentType | integer | 1 = event, 2 = task, 3 = note, 4 = birthday |
| Flags | ||
| DateStart | integer | UTC start date in Unix Time Format (number of seconds since 01/01/1970) |
| DateEnd | integer | -1 = undefined, otherwise UTC end date in Unix Time Format (number of seconds since 01/01/1970) |
| Summary | text | title [event, task, note, birthday] |
| Location | text | location [event] |
| Description | text | comments [event, task, note] |
| Status | integer | -1 = undefined [event, note]. 0 = incomplete [task], 1 = complete [task], yyyy = year [birthday] |
| Uid | ||
| Until | integer | -1 = none [event, tastk, note], 2145913199 = end of calendar / limit of the Unix Time Format, other integer = end date of a recurrence [event, birthday] |
| AllDay | integer | 0 = in limited time [event, task, note], 1 = all day [event, birthday] |
| CreatedTime | integer | date of creation |
| ModifiedTime | integer | last date of modification |
| Tzid | text | time zone identifier, for example "Europe/Paris"
|
| TzOffset | text | time zone offset in seconds compared to UTC, for example "7200" (2 hours)
|