Old CalendarDatabaseSchema: Difference between revisions

From Open-Xchange
(add description for field06)
 
(13 intermediate revisions by 2 users not shown)
Line 18: Line 18:
|| changing_date || Timestamp with time zone || The date when this appointment was modified last
|| changing_date || Timestamp with time zone || The date when this appointment was modified last
|-
|-
|| user_right || Text || Owner of the of the appointment.
|| user_right || Text || Owner of the of the appointment. <BR> Is normally the same like the UID in created_from except in a private shared folder when the appointment was created by another user that is not the owner of the shared folder.  
Is normally the same like the UID in created_from except in a private shared folder when the appointment was created by another user
that is not the owner of the shared folder.  
|-
|-
|| group_right || Text || Possible values are "s" for appointment with one use and "g" for group appointment
|| group_right || Text || Possible values are "s" for appointment with one use and "g" for group appointment
Line 28: Line 26:
|| tid || Text || The folder id where the appointment was saved (i.e. the ID of the calendar-folder)
|| tid || Text || The folder id where the appointment was saved (i.e. the ID of the calendar-folder)
|-
|-
|| fid || Number || The folder id where the appointment was saved.
|| fid || Number || The folder id where the appointment was saved.<BR> If the appointment was stored in a private folder the folder id is always "-1".
If the appointment was stored in a private folder the folder id is always "-1".
If the appointment was stored in a public folder the folder id is the id of the public folder and therefore equals with tid
If the appointment was stored in a public folder the folder id is the id of the public folder and therefore equals with tid
|-
|-
|| order_crit ||Text || Not unused anymore
|| order_crit ||Text || Unused
|-
|-
|| timestampfield01 || Timestamp with time zone || starting time
|| timestampfield01 || Timestamp with time zone || The starting time of the appointment.
If field05 doesn't contain the value 'gtz' the normal starting time is saved.
e.g. Start date is "10.08.2007 10:00:00+02" the value is saved in this way in the database "2007-08-10 10:00:00+02".
Otherwiese if field05 contains the value 'gtz' is only the date without time but with server offset saved.
e.g. Start date is "10.08.2007" the value is saved in this way in the database "2007-08-10 00:00:00+02".
If the server timezone is "Europe/Berlin"
|-
|-
|| timestampfield02||timestamp with time zone|| ending time
|| timestampfield02 || Timestamp with time zone || The ending time of the appointment. <BR> If non recurring appointments are stored this field stores the values of the end time like the start time see information for timestampfield01.
The only exception is if a recurring appointment is saved. In this case if the value of timestampfield02 the until date of the recurrence appointment plus the appointment end time.
This means in the case we have a start date = 10.08.2007 10:00, an end date = 10.08.2007 11:00 and an until = 16.08.2007 the stored value in the database is "2007-08-16 11:00:00+02".
|-
|-
| intfield01 || Integer || The unique id of the appointment
| intfield01 || Integer || The unique id of the appointment
|-
|-
|| intfield02 || Integer || Only used if the appointment was a recurrence or an exception of an recurrence appointment.  
|| intfield02 || Integer || Only used if the appointment was a recurrence or an exception of an recurrence appointment. <BR> There are three diffenrent cases:<BR>
There are three diffenrent cases:
Case one is that is it a normal appointment. In this case is the value of intfield02 NULL.<BR>
Case one is that is it a normal appointment. In this case is the value of intfield02 NULL.
Case two is the main recurrence appointment. In this case is the value of intfield02 the same like intfield01.<BR>
Case two is the main recurrence appointment. In this case is the value of intfield02 the same like intfield01.
Case three is an exception of a recurrence appointment. In this case is the value of intfield02 the value of intfield01 from the main recurrence appointment.
Case three is an exception of a recurrence appointment.  
In this case is the value of intfield02 the value of intfield01 from the main recurrence appointment.
|-
|-
|| intfield03 || Integer || Unused
|| intfield03 || Integer || Color label
|-
|-
|| intfield04 || Integer || The duration of the appointment in days.  
|| intfield04 || Integer || The duration of the appointment in days. <BR> Is used if the appointment is a recurrence because in this case the field timestampfield02 stores end date of recurrence
Is used if the appointment is a recurrence because in this case the field timestampfield02 stores end date of recurrence
|-
|-
|| intfield05 || Integer || The recurrence position of an exception from a recurrence appointment.
|| intfield05 || Integer || The recurrence position of an exception from a recurrence appointment, 0 if it is the main sequence. <BR> Must be NULL if it is a normal appointment.
Must be > 1 or NULL if it is a normal appointment.
|-
|-
|| intfield06 || Integer || Not used anymore
|| intfield06 || Integer || Not used anymore
|-
|-
|| intfield07 || Integer || Unused
|| intfield07 || Integer || Number of Attachments
|-
|-
|| field01 || Text || The subject of the appointment. This field must not be null.
|| field01 || Text || The subject of the appointment. This field must not be null.
Line 64: Line 64:
|-
|-
|| field03 || Text || 'Display As'-Type holds possible values are:
|| field03 || Text || 'Display As'-Type holds possible values are:
date1 = Reserved
date1 = Reserved<BR>
 
date2 = Temporary<BR>
date2 = Temporary
date3 = Absent<BR>
 
date3 = Absent
 
date4 = free
date4 = free
|-
|-
Line 76: Line 73:
|| field05 || Text || Possible values are 'gtz' if the appointment is stored as a full time appointment or NULL if it is a normal appointment.
|| field05 || Text || Possible values are 'gtz' if the appointment is stored as a full time appointment or NULL if it is a normal appointment.
|-
|-
|| field06 || Text || Holds a string representation of the recurrence information.  
|| field06 || Text || Holds a string representation of the recurrence information. <BR> All attributes in this string are seperated with a <nowiki>"|"</nowiki>. A detailed description of the attributes is descriped in [[#RecurrenceFieldAttributes | Recurrence field attributes]].
All attributes in this string are seperated with a "|".  
A detailed description of the attributes is descriped in [[#RecurrenceFieldAttributes | Recurrence field attributes]].


This field must not be NULL.
This field must not be NULL.
|-
|-
|| field07 || Text || Comma-separated list of sequence numbers.  
|| field07 || Text || Comma-separated list of sequence numbers. <BR> Every number is the position of a deleted appointment of the recurrence appointment.
Every number is the position of a deleted appointment of the recurrence appointment.
|-
|-
|| field08 || Text || Comma-separated list of a id's.
|| field08 || Text || Comma-separated list of a id's.
Every id is a reference of a modified exception of the recurrence appointment.
Every id is a reference of a modified exception of the recurrence appointment.
|-
|-
|| field09 || Text || Unused
|| field09 || Text || Categories
|-
|-
|| field10 || Text || Completely unused
|| field10 || Text || Comma-separated list of a sequence numbers. <BR> Every number is the position of a changed appointment of the recurrence appointment.
|-
|-
|| field11 || Text || Completely unused
|| field11 || Text || Completely unused
Line 100: Line 94:
|| field14 || Text || Completely unused
|| field14 || Text || Completely unused
|-
|-
|| field15 || Text || Completely unused
|| field15 || Text || "1" if the appointment was stored in a 0.8.8 version. Null otherwise.
|-
|| confidential || Text || The private flag of the appointment. Possible values are yes or no
|-
|| confirmnotification || Text || Enables the confirm notification for the user. Possible values are yes or no
|}
|}


Line 107: Line 105:
! Attribute !! Type !! Description
! Attribute !! Type !! Description
|-
|-
| ds || Text || Possible values no, daily, weekly, monthly or yearly
| ds || Text || Possible values no, daily, weekly, monthly, monthly2, yearly or yearly2
|-
|-
| ds_ends || Long || Milliseconds from 01.01.1970 in UTC.  
| ds_ends || Long || Milliseconds from 01.01.1970 in UTC. <BR> The long descripes the end date of the recurrence appointment.  
The long descripes the end date of the recurrence appointment.  
The end date must be a date without times.
The end date must be a date without times.
|-
|-
| ds_start || Long || Milliseconds from 01.01.1970 in UTC.  
| ds_start || Long || Milliseconds from 01.01.1970 in UTC. <BR> The long descripes the start date of the recurrence appointment.  
The long descripes the start date of the recurrence appointment.  
The start date must be a date without times.
The start date must be a date without times.
|-
|-
Line 121: Line 117:
| weekly_value || Integer || The recurrence interval for weekly appointments
| weekly_value || Integer || The recurrence interval for weekly appointments
|-
|-
| weekly_day_1 || Integer || Can only be the value "1".  
| weekly_day_1 || Integer || Can only be the value "1". <BR> If this attributes exists the sunday if enabled for the weekly recurrence.
If this attributes exists the sunday if enabled for the weekly recurrence.
|-
|-
| weekly_day_2 || Integer || Can only be the value "2".  
| weekly_day_2 || Integer || Can only be the value "2". <BR> If this attributes exists the monday if enabled for the weekly recurrence.
If this attributes exists the monday if enabled for the weekly recurrence.
|-
|-
| weekly_day_3 || Integer || Can only be the value "3".  
| weekly_day_3 || Integer || Can only be the value "3". <BR> If this attributes exists the tuesday if enabled for the weekly recurrence.
If this attributes exists the tuesday if enabled for the weekly recurrence.
|-
|-
| weekly_day_4 || Integer || Can only be the value "4".  
| weekly_day_4 || Integer || Can only be the value "4". <BR> If this attributes exists the wednesday if enabled for the weekly recurrence.
If this attributes exists the wednesday if enabled for the weekly recurrence.
|-
|-
| weekly_day_5 || Integer || Can only be the value "5".  
| weekly_day_5 || Integer || Can only be the value "5". <BR> If this attributes exists the thursday if enabled for the weekly recurrence.
If this attributes exists the thursday if enabled for the weekly recurrence.
|-
|-
| weekly_day_6 || Integer || Can only be the value "6".  
| weekly_day_6 || Integer || Can only be the value "6". <BR> If this attributes exists the friday if enabled for the weekly recurrence.
If this attributes exists the friday if enabled for the weekly recurrence.
|-
|-
| weekly_day_7 || Integer || Can only be the value "7".  
| weekly_day_7 || Integer || Can only be the value "7". <BR> If this attributes exists the saturday if enabled for the weekly recurrence.
If this attributes exists the saturday if enabled for the weekly recurrence.
|-
|-
| monthly_value_month || Integer || The recurrence interval for monthly appointments.  
| monthly_value_month || Integer || The recurrence interval for monthly appointments.  
Line 147: Line 136:
| monthly_value_day || Integer || Day in month when the appointment is shown
| monthly_value_day || Integer || Day in month when the appointment is shown
|-
|-
| monthly2_value_month || Integer || The recurrence interval for monthly appointments.  
| monthly2_value_month || Integer || The recurrence interval for monthly appointments. <BR> Is used in comination with "monthly2_day" and "monthly_recurrency"
Is used in comination with "monthly2_day" and "monthly_recurrency"
|-
|-
| monthly2_day || Integer || Possible values are:
| monthly2_day || Integer || Possible values are:
1 = Sunday
1 = Sunday<BR>
 
2 = Monday<BR>
2 = Monday
3 = Tuesday<BR>
 
4 = Wednesday<BR>
3 = Tuesday
5 = Thursday<BR>
 
6 = Friday<BR>
4 = Wednesday
7 = Saturday<BR>
 
-1 = Day<BR>
5 = Thurday
-2 = Weekday<BR>
 
-3 = Weekend day<BR>
6 = Friday
 
7 = Saturday
 
-1 = Day
 
-2 = Weekday
 
-3 = Weekend day
 
|-
|-
| monthly2_reccurency || Integer || Possible values are:
| monthly2_reccurency || Integer || Possible values are:
1 = First occurrence
1 = First occurrence<BR>
 
2 = Second occurrence<BR>
2 = Second occurrence
3 = Third occurrence<BR>
 
4 = Forth occurrence<BR>
3 = Third occurrence
-1 = Last occurrence<BR>
 
4 = Forth occurrence
 
-1 = Last occurrence
 
|-
|-
| yearly_value_day || Integer || Day in month when the appointment is shown.
| yearly_value_day || Integer || Day in month when the appointment is shown. <BR> Only in combination with ds=yearly and yearly_month
Only in combination with ds=yearly and yearly_month
|-
|-
| yearly_month || Integer || The month when the appointment is shown. Possible values are:
| yearly_month || Integer || The month when the appointment is shown. Possible values are:
0 = January
0 = January<BR>
 
1 = February<BR>
1 = February
2 = March<BR>
 
3 = April<BR>
2 = March
4 = May<BR>
 
5 = June<BR>
3 = April
6 = July<BR>
 
7 = August<BR>
4 = May
8 = September<BR>
 
9 = October<BR>
5 = June
10 = November<BR>
 
11 = December<BR>
6 = July
 
7 = August
 
8 = September
 
9 = October
 
10 = November
 
11 = December
|-
|-
| yearly2_reccurency || Integer || Possible values are:
| yearly2_reccurency || Integer || Possible values are:
1 = First occurrence
1 = First occurrence<BR>
 
2 = Second occurrence<BR>
2 = Second occurrence
3 = Third occurrence<BR>
 
4 = Forth occurrence<BR>
3 = Third occurrence
-1 = Last occurrence<BR>
 
4 = Forth occurrence
 
-1 = Last occurrence
|-
|-
| yearly2_day || Integer || Possible values are:
| yearly2_day || Integer || Possible values are:
1 = Sunday
1 = Sunday<BR>
 
2 = Monday<BR>
2 = Monday
3 = Tuesday<BR>
 
4 = Wednesday<BR>
3 = Tuesday
5 = Thursday<BR>
 
6 = Friday<BR>
4 = Wednesday
7 = Saturday<BR>
 
-1 = Day<BR>
5 = Thurday
-2 = Weekday<BR>
 
-3 = Weekend day<BR>
6 = Friday
 
7 = Saturday
 
-1 = Day
 
-2 = Weekday
 
-3 = Weekend day
|-
|-
| yearly2_month || Integer || Possible values are:
| yearly2_month || Integer || Possible values are:
0 = January
0 = January<BR>
1 = February<BR>
2 = March<BR>
3 = April<BR>
4 = May<BR>
5 = June<BR>
6 = July<BR>
7 = August<BR>
8 = September<BR>
9 = October<BR>
10 = November<BR>
11 = December<BR>
|}


1 = February
===Table: prg_dates_members===
This table contains all user participant of the appointment with the attributes displayname, confirm, confirm reason and the personal folder id. Detailed informations about all fields are described in the table below [[#prg_dates_members_structure | prg_dates_member structure]].


2 = March
{| id="prg_dates_members_structure" cellspacing="0" border="1" width="80%"
|+ align="bottom" | prg_dates data structure
! Field !! Type !! Description
|-
| object_id || Integer || A reference to the appointment id (prg_dates.intfield01)
|-
| member_uid || Text || The UID of user participant or an email address if the participant is an external participant.
|-
| member_name || Text || The display name of the user participant or NULL if the participant is an external participant.
|-
| confirm || Text || Possible values are:
n = no confirmation


3 = April
t = accepted


4 = May
f = declined
|-
| reason || Text || The confirm reason if the user has accepted or declined
|-
| pfid || Integer || The personal folder of the user or a -99 if the participant is an external participant.
|}


5 = June
===Table: prg_dates_resources===
This table contains all resource or resource group participants of an appointment. Detailed informations about all fields in the table prg_dates_resources are described in the table below [[#prg_dates_resources_structure | prg_dates_resources structure]].


6 = July
{| id="prg_dates_resources_structure" cellspacing="0" border="1" width="80%"
|+ align="bottom" | prg_dates_resources data structure
! Field !! Type !! Description
|-
| object_id || Integer || A reference to the appointment id (prg_dates.intfield01)
|-
| group_right || Text || The resource group id. If this value is set the field user_right must be null.
|-
| user_right || Text || The resource id. If this value is set the field group_right must be null.
|}


7 = August
===Table: prg_date_rights===
This table contains the user and group participant of an appointment without resolving the members of the group. Detailed informations about all fields in the table prg_date_rights are described in the table below [[#prg_date_rights_structure | prg_date_rights structure]].


8 = September
{| id="prg_date_rights_structure" cellspacing="0" border="1" width="80%"
|+ align="bottom" | prg_date_rights data structure
! Field !! Type !! Description
|-
| object_id || Integer || A reference to the appointment id (prg_dates.intfield01)
|-
| group_right || Text || The group id. If this value is set the field user_right must be null.
|-
| user_right || Text || The user id (UID). If this value is set the field group_right must be null.
|}


9 = October
===Table: prg_date_notification===
This table contains the alarm for all user participants of the appointment. Detailed informations about all fields in the table prg_date_notification are described in the table below [[#prg_date_notification_structure | prg_date_notification structure]].


10 = November
{| id="prg_date_notification_structure" cellspacing="0" border="1" width="80%"
 
|+ align="bottom" | prg_date_notification data structure
11 = December
! Field !! Type !! Description
|-
| object_id || Integer || A reference to the appointment id (prg_dates.intfield01)
|-
| member_uid || Text || The user id (UID).
|-
| notification || Text || The alarm in minutes before the start of the appointment.
|}
|}
===Table: prg_dates_members===
In progress
===Table: prg_date_resources===
In progress
===Table: prg_date_rights===
In progress
===Table: prg_date_notification===


===Table: prg_dates_times===
===Table: prg_dates_times===
This table is not used anymore
This table is not used anymore

Latest revision as of 12:40, 27 February 2008

Calendar Database Schema informations

This page contains all informations about the internal structure of appointments and related object and some other useful informations about the content of the tables use by the calendar module.

Table prg_dates

The main table of appointments a detailed description which information are stored in this table is described in the table prg_dates structure.

prg_dates data structure
Field Type Description
created_from Text UID of the user who created this appointment (e.g. 'sally')
creating_date Timestamp with time zone The date when this appointment was created
changed_from Text UID of user who modified this appointment last (e.g. 'peter')
changing_date Timestamp with time zone The date when this appointment was modified last
user_right Text Owner of the of the appointment.
Is normally the same like the UID in created_from except in a private shared folder when the appointment was created by another user that is not the owner of the shared folder.
group_right Text Possible values are "s" for appointment with one use and "g" for group appointment
sid Text Unused
tid Text The folder id where the appointment was saved (i.e. the ID of the calendar-folder)
fid Number The folder id where the appointment was saved.
If the appointment was stored in a private folder the folder id is always "-1".

If the appointment was stored in a public folder the folder id is the id of the public folder and therefore equals with tid

order_crit Text Unused
timestampfield01 Timestamp with time zone The starting time of the appointment.

If field05 doesn't contain the value 'gtz' the normal starting time is saved. e.g. Start date is "10.08.2007 10:00:00+02" the value is saved in this way in the database "2007-08-10 10:00:00+02". Otherwiese if field05 contains the value 'gtz' is only the date without time but with server offset saved. e.g. Start date is "10.08.2007" the value is saved in this way in the database "2007-08-10 00:00:00+02". If the server timezone is "Europe/Berlin"

timestampfield02 Timestamp with time zone The ending time of the appointment.
If non recurring appointments are stored this field stores the values of the end time like the start time see information for timestampfield01.

The only exception is if a recurring appointment is saved. In this case if the value of timestampfield02 the until date of the recurrence appointment plus the appointment end time. This means in the case we have a start date = 10.08.2007 10:00, an end date = 10.08.2007 11:00 and an until = 16.08.2007 the stored value in the database is "2007-08-16 11:00:00+02".

intfield01 Integer The unique id of the appointment
intfield02 Integer Only used if the appointment was a recurrence or an exception of an recurrence appointment.
There are three diffenrent cases:

Case one is that is it a normal appointment. In this case is the value of intfield02 NULL.
Case two is the main recurrence appointment. In this case is the value of intfield02 the same like intfield01.
Case three is an exception of a recurrence appointment. In this case is the value of intfield02 the value of intfield01 from the main recurrence appointment.

intfield03 Integer Color label
intfield04 Integer The duration of the appointment in days.
Is used if the appointment is a recurrence because in this case the field timestampfield02 stores end date of recurrence
intfield05 Integer The recurrence position of an exception from a recurrence appointment, 0 if it is the main sequence.
Must be NULL if it is a normal appointment.
intfield06 Integer Not used anymore
intfield07 Integer Number of Attachments
field01 Text The subject of the appointment. This field must not be null.
field02 Text Location
field03 Text 'Display As'-Type holds possible values are:

date1 = Reserved
date2 = Temporary
date3 = Absent
date4 = free

field04 Text Comment/Note
field05 Text Possible values are 'gtz' if the appointment is stored as a full time appointment or NULL if it is a normal appointment.
field06 Text Holds a string representation of the recurrence information.
All attributes in this string are seperated with a "|". A detailed description of the attributes is descriped in Recurrence field attributes.

This field must not be NULL.

field07 Text Comma-separated list of sequence numbers.
Every number is the position of a deleted appointment of the recurrence appointment.
field08 Text Comma-separated list of a id's.

Every id is a reference of a modified exception of the recurrence appointment.

field09 Text Categories
field10 Text Comma-separated list of a sequence numbers.
Every number is the position of a changed appointment of the recurrence appointment.
field11 Text Completely unused
field12 Text Completely unused
field13 Text Completely unused
field14 Text Completely unused
field15 Text "1" if the appointment was stored in a 0.8.8 version. Null otherwise.
confidential Text The private flag of the appointment. Possible values are yes or no
confirmnotification Text Enables the confirm notification for the user. Possible values are yes or no
Recurrence field attributes
Attribute Type Description
ds Text Possible values no, daily, weekly, monthly, monthly2, yearly or yearly2
ds_ends Long Milliseconds from 01.01.1970 in UTC.
The long descripes the end date of the recurrence appointment.

The end date must be a date without times.

ds_start Long Milliseconds from 01.01.1970 in UTC.
The long descripes the start date of the recurrence appointment.

The start date must be a date without times.

daily_value Integer The recurrence interval for daily appointments
weekly_value Integer The recurrence interval for weekly appointments
weekly_day_1 Integer Can only be the value "1".
If this attributes exists the sunday if enabled for the weekly recurrence.
weekly_day_2 Integer Can only be the value "2".
If this attributes exists the monday if enabled for the weekly recurrence.
weekly_day_3 Integer Can only be the value "3".
If this attributes exists the tuesday if enabled for the weekly recurrence.
weekly_day_4 Integer Can only be the value "4".
If this attributes exists the wednesday if enabled for the weekly recurrence.
weekly_day_5 Integer Can only be the value "5".
If this attributes exists the thursday if enabled for the weekly recurrence.
weekly_day_6 Integer Can only be the value "6".
If this attributes exists the friday if enabled for the weekly recurrence.
weekly_day_7 Integer Can only be the value "7".
If this attributes exists the saturday if enabled for the weekly recurrence.
monthly_value_month Integer The recurrence interval for monthly appointments.

Is used in comination with "monthly_value_day"

monthly_value_day Integer Day in month when the appointment is shown
monthly2_value_month Integer The recurrence interval for monthly appointments.
Is used in comination with "monthly2_day" and "monthly_recurrency"
monthly2_day Integer Possible values are:

1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
-1 = Day
-2 = Weekday
-3 = Weekend day

monthly2_reccurency Integer Possible values are:

1 = First occurrence
2 = Second occurrence
3 = Third occurrence
4 = Forth occurrence
-1 = Last occurrence

yearly_value_day Integer Day in month when the appointment is shown.
Only in combination with ds=yearly and yearly_month
yearly_month Integer The month when the appointment is shown. Possible values are:

0 = January
1 = February
2 = March
3 = April
4 = May
5 = June
6 = July
7 = August
8 = September
9 = October
10 = November
11 = December

yearly2_reccurency Integer Possible values are:

1 = First occurrence
2 = Second occurrence
3 = Third occurrence
4 = Forth occurrence
-1 = Last occurrence

yearly2_day Integer Possible values are:

1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
-1 = Day
-2 = Weekday
-3 = Weekend day

yearly2_month Integer Possible values are:

0 = January
1 = February
2 = March
3 = April
4 = May
5 = June
6 = July
7 = August
8 = September
9 = October
10 = November
11 = December

Table: prg_dates_members

This table contains all user participant of the appointment with the attributes displayname, confirm, confirm reason and the personal folder id. Detailed informations about all fields are described in the table below prg_dates_member structure.

prg_dates data structure
Field Type Description
object_id Integer A reference to the appointment id (prg_dates.intfield01)
member_uid Text The UID of user participant or an email address if the participant is an external participant.
member_name Text The display name of the user participant or NULL if the participant is an external participant.
confirm Text Possible values are:

n = no confirmation

t = accepted

f = declined

reason Text The confirm reason if the user has accepted or declined
pfid Integer The personal folder of the user or a -99 if the participant is an external participant.

Table: prg_dates_resources

This table contains all resource or resource group participants of an appointment. Detailed informations about all fields in the table prg_dates_resources are described in the table below prg_dates_resources structure.

prg_dates_resources data structure
Field Type Description
object_id Integer A reference to the appointment id (prg_dates.intfield01)
group_right Text The resource group id. If this value is set the field user_right must be null.
user_right Text The resource id. If this value is set the field group_right must be null.

Table: prg_date_rights

This table contains the user and group participant of an appointment without resolving the members of the group. Detailed informations about all fields in the table prg_date_rights are described in the table below prg_date_rights structure.

prg_date_rights data structure
Field Type Description
object_id Integer A reference to the appointment id (prg_dates.intfield01)
group_right Text The group id. If this value is set the field user_right must be null.
user_right Text The user id (UID). If this value is set the field group_right must be null.

Table: prg_date_notification

This table contains the alarm for all user participants of the appointment. Detailed informations about all fields in the table prg_date_notification are described in the table below prg_date_notification structure.

prg_date_notification data structure
Field Type Description
object_id Integer A reference to the appointment id (prg_dates.intfield01)
member_uid Text The user id (UID).
notification Text The alarm in minutes before the start of the appointment.

Table: prg_dates_times

This table is not used anymore

Retrieved from "https://wiki.open-xchange.com/wiki/index.php?title=Old_CalendarDatabaseSchema&oldid=1410"