Deliverables database table
From TaskDepender
(→Description) |
|||
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
| − | + | The deliverable component is described in [[Task_Management_Method#Deliverable|"Task Management Method"]]. The deliverables in the project are stored in a table in the project database. Since the name does not have to be unique, a deliverable has to have a unique id which can be generated as a integer primary key [http://www.sqlite.org/lang_createtable.html#rowid] by the database [http://www.sqlite.org/lang_createtable.html#rowid]. Since a deliverable represents a graphical element, it has a position, a width and a height. When using a true-type font, the width and height will be determined when the task is displayed. | |
| − | * When | + | |
| + | == Constraints == | ||
| + | |||
| + | The following constraints apply for the deliverables table: | ||
| + | * When a container task is deleted, the contained tasks need to be deleted as well. | ||
| + | * When the connection between the parent and the connected task is deleted, a [[Clone|cloned deliverable]] must be deleted as well. | ||
| + | * When a deliverable is deleted, all its connections are deleted as well. | ||
== Design == | == Design == | ||
| − | The | + | The <tt>Deliverables</tt> table has the following fields: |
{| valign="top" border="1" cellpadding="3" cellspacing="0" | {| valign="top" border="1" cellpadding="3" cellspacing="0" | ||
| Line 20: | Line 26: | ||
| <tt>Description</tt>|| text || [[System Data Format|SDF string]]. | | <tt>Description</tt>|| text || [[System Data Format|SDF string]]. | ||
|- valign="top" | |- valign="top" | ||
| − | | <tt> | + | | <tt>X</tt> || integer || The x-coordinate of the deliverable in the diagram, expressed in pixels. |
|- valign="top" | |- valign="top" | ||
| − | | <tt> | + | | <tt>Y</tt> || integer || The y-coordinate of the deliverable in the diagram, expressed in pixels. |
|- valign="top" | |- valign="top" | ||
| − | | <tt> | + | | <tt>Width</tt> || integer || The width of the deliverable in the diagram, expressed in pixels. |
| + | |- valign="top" | ||
| + | | <tt>Height</tt> || integer || The height of the deliverable in the diagram, expressed in pixels. | ||
|- valign="top" | |- valign="top" | ||
| <tt>ContainerId</tt> || integer || The id of the container task. Set to 0 if defined at the top level. | | <tt>ContainerId</tt> || integer || The id of the container task. Set to 0 if defined at the top level. | ||
| Line 31: | Line 39: | ||
|- valign="top" | |- valign="top" | ||
| <tt>Available</tt> || integer || Whether or not the deliverable is ready to be used as input for the dependent task. | | <tt>Available</tt> || integer || Whether or not the deliverable is ready to be used as input for the dependent task. | ||
| + | |- valign="top" | ||
| + | | <tt>ConnectionId</tt> || integer || If the deliverable is a clone, this value in not 0 and indicates the id of the entry in the [[Connections database table|connection]]. | ||
|} | |} | ||
| − | |||
| − | + | The following actions are defined: | |
| + | * [[Deliverables database table - Create|Create]] | ||
| + | * [[Deliverables database table - Insert|Insert]] | ||
| + | * [[Deliverables database table - Update|Update]] | ||
| + | * [[Deliverables database table - Delete|Delete]] | ||
| + | * [[Deliverables database table - Cut|Cut]] | ||
| + | * [[Deliverables database table - Paste|Paste]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
---- | ---- | ||
| − | |||
* [[Database]] | * [[Database]] | ||
