This file is generated from tables-mysql.sql. Below are the definitions of all WebCalendar tables along with some descriptions of how each table is used. Column names shown in red are the primary keys for that table.

If you update the SQL for WebCalendar, use the sql2html.pl script to regenerate this file.

Define assitant/boss relationship.

Defines user categories. Categories can be specific to a user or global. When a category is global, the cat_owner field will be NULL. (Only an admin user can create a global category.)

System settings (set by the admin interface in admin.php)

Defines a calendar event. Each event in the system has one entry in this table unless the event starts before midnight and ends after midnight. In that case a secondary event will be created with cal_ext_for_id set to the cal_id of the original entry. The following tables contain additional information about each event:

• webcal_entry_user - lists participants in the event and specifies the status (accepted, rejected) and category of each participant.
• webcal_entry_repeats - contains information if the event repeats.
• webcal_entry_repeats_not - specifies which dates the repeating event does not repeat (because they were deleted or modified for just that date by the user)
• webcal_entry_log - provides a history of changes to this event.
• webcal_site_extras - stores event data as defined in site_extras.php (such as reminders and other custom event fields).

This table associates one or more external users (people who do not have a WebCalendar login) with an event by the event id. An event must still have at least one WebCalendar user associated with it. This table is not used unless external users are enabled in system settings. The event can be found in webcal_entry.

Activity log for an event.

Defines repeating info about an event. The event is defined in webcal_entry.

This table specifies which dates in a repeating event have either been deleted or replaced with a replacement event for that day. When replaced, the cal_group_id (I know… not the best name, but it was not being used) column will be set to the original event. That way the user can delete the original event and (at the same time) delete any exception events.

This table associates one or more users with an event by the event id. The event can be found in webcal_entry.

Define a group. Group members can be found in webcal_group_user.

Specify users in a group. The group is defined in webcal_group.

Used to track import data (one row per import)

Used to track import data (one row per event)

Defines non-user calendars.

This table keeps a history of when reminders get sent.

Defines a custom report created by a user.

Defines one of the templates used for a report. Each report has three templates:

1. Page template - Defines the entire page (except for header and footer). The following variables can be defined:
   • ${days}^* - the HTML of all dates (generated from the Date template)
2. Date template - Defines events for one day. If the report is for a week or month, then the results of each day will be concatenated and used as the ${days} variable in the Page template. The following variables can be defined:
   • ${events}^* - the HTML of all events for the data (generated from the Event template)
   • ${date} - the date
   • ${fulldate} - date (includes weekday)
3. Event template - Defines a single event. The following variables can be defined:
   • ${name}^* - Brief Description of event
   • ${description} - Full Description of event
   • ${date} - Date of event
   • ${fulldate} - Date of event (includes weekday)
   • ${time} - Time of event (4:00pm - 4:30pm)
   • ${starttime} - Start time of event
   • ${endtime} - End time of event
   • ${duration} - Duration of event (in minutes)
   • ${priority} - Priority of event
   • ${href} - URL to view event details

^* denotes a required template variable

This table holds data for site extra fields (customized in site_extra.php).

Defines a WebCalendar user.

Define layers for a user.

Specify preferences for a user. Most preferences are set via pref.php. Values in this table are loaded after system settings found in webcal_config.

A “view” allows a user to put the calendars of multiple users all on one page. A “view” is valid only for the owner (cal_owner) of the view. Users for the view are in webcal_view_user.

Specify users in a view. See webcal_view.