Tasks database table
From TaskDepender
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
| − | The task element is described in the [[Task_Management_Method#Task|"Task Management Method"]]. The tasks in the project are stored in a table in the project database. The name does not have to be unique. Therefore, a task also has to have a unique id. Further, since a task represents a graphical element, it has a position, a width and a height. These attributes are expressed in pixels. The TaskDepender™ program uses a true-type font, and therefore the width and height will be determined when the task is displayed. | + | The task element is described in the [[Task_Management_Method#Task|"Task Management Method"]]. The tasks in the project are stored in a table in the project database. The name of a task does not have to be unique. Therefore, a task also has to have a unique id. Further, since a task represents a graphical element, it has a position, a width and a height. These attributes are expressed in pixels. The TaskDepender™ program uses a true-type font, and therefore the width and height will be determined when the task is displayed. |
| − | The following constraints apply for the : | + | The following constraints apply for the tasks table: |
* When a container task is deleted, the contained tasks need to be deleted as well. | * When a container task is deleted, the contained tasks need to be deleted as well. | ||
* When a resource is deleted that is the responsible resource for a task, the resource is set to undefined. | * When a resource is deleted that is the responsible resource for a task, the resource is set to undefined. | ||
