 |
 |
 |
 |
|
 |
 |
Gravitybox Schedule.NET
1998-2005 Gravitybox Software LLC
Page 65 of 90
Alarm_Is_Armed
Boolean
No
Alarm_Reminder
Integer
No
Alarm_Allow_Open
Boolean
No
Alarm_Allow_Snooze
Boolean
No
Alarm_Was_Dismissed
Boolean
No
Although appointments are the most important table, you may also bind to other dataset
tables as well. The Room table must have a room_guid and name, both of type string,
set to not accept null values. It may also have an optional notes field of type string. The
Appointment table has a direct reference to the Room table. It has a Room_guid field
that may be null, signifying no room is associated with the appointment or it may have a
room_guid mapping to the Room table. This is a one-to-many relationship. An
appointment is associated with exactly zero or one room.
Room Data Table
Field
Data Type
Required / Non-Null
Room_Guid
String
Yes (pk)
Name
String
Yes
Notes
String
No
The Provider table has the same format and rules of the Room table with the additional,
non-nullable, required integer field of Color. Both the Provider and Category tables differ
in their association to the Appointment table as compared to the Room table. While an
appointment can have at most one room, it can have any number of providers or
categories associated with it. This is a many-to-many relationship. Because of this more
complicated relationship, there is needed an intermediary table necessary. For the
Provider table the intermediary is the Appointment_Provider table. This table holds
nothing more a reference to the appointment and provider tables. These two fields
make up a composite, non-unique key. The Category and Appointment_Category tables
are much the same.
Provider Data Table
Field
Data Type
Required / Non-Null
Provider_Guid
String
Yes (pk)
Name
String
Yes
Color
Integer
Yes
Notes
String
No
Appointment_Provider Table
Field
Data Type
Required / Non-Null
Appointment_Guid
String
Yes (pk)
Provider_Guid
String
Yes (pk)