Is it a good practice to maintain the data in a separate table from the task table?

Question

In my application there is a module which displays info by reading from a table. This info can be edited. Once edited there is a series of actions needs to be performed. So i am maintaining a task table which will create task for each edit made. In order to execute the task, i need the data modified by the user along with the user id. My task table structure will be like this:

TaskId 
TaskType
CreatedOn
State
CompletedOn

I am planning to have TaskType attribute based on which it will read the data from the source data table on which info is stored. Now my question is, i also need to maintain the userid to know for which user i have to fetch the data from the source data table? I don want to maintain that in TaskTable then it would become a Task of particular type. Can someone suggest on good approach for this?

Answer 1

0

You might want a TaskProcess table that is a one to many to the Task table with a foreign key on TaskID. The TaskProcess table can track the processing done on the task with a UserID , Action and Completed (boolean) as columns.

answered Nov 19 '12 at 03:05 PM

TheSmilingDBA
81 ● 1 ● 1 ● 2

(comments are locked)

Is it a good practice to maintain the data in a separate table from the task table?

Follow this question

Related Questions