Member_2_8034623
asked on
Table formats and best practices
Hi,
I am curious about best practices
Scenario:
Want to be able to track group task and personal tasks
Details
Im curious if it is better practice to great three tables like so
tables
Or to separate the tasks table into two tables one for users and one for groups (assignments would only be associated to the second table)
Thanks in advance!!
I am curious about best practices
Scenario:
Want to be able to track group task and personal tasks
Details
- Group tasks are independent of personal tasks
- Group tasks can be assigned to a person
- Task assignments are only at the group level
- Personal tasks are automatically assigned to that user
- Personal tasks only apply to that person
- The columns within the tasks table would be identical for both personal and group with exception of the ID (group/user)
Im curious if it is better practice to great three tables like so
tables
- entity type (ex: 1 = group, 2 = user)
- tasks -> add an additional field to compensate for entity type
- tasks-assignments
Or to separate the tasks table into two tables one for users and one for groups (assignments would only be associated to the second table)
Thanks in advance!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can a task be linked to more than one group?
ASKER
Hi,
Group tasks are unique to each group
Later i want to expand the capabilities of the tasks. Where a group can be divided into subgroups and then the task could then be assigned to subgroups and players within the larger group. Currently, this is not supported.
Could you please elaborate? im not sure what you mean.
Group tasks are unique to each group
Later i want to expand the capabilities of the tasks. Where a group can be divided into subgroups and then the task could then be assigned to subgroups and players within the larger group. Currently, this is not supported.
Depending on your data models and needs, you may not even need the Entity Type table. If this is going to just be a single column table, then it may be redundant altogether - just store it in the Task table.
Could you please elaborate? im not sure what you mean.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.