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

  • 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?

  • Do humans need to perform these tasks on particular edits or does the system? The approach will vary widely depending on the two.

    If the system needs to perform a task series, you'll have to give us a lot better explanation of what's going on, the schema, and what you need it to end up doing. The Task Table is both overkill and at best a logging tool at that point.

    If users need to perform these tasks, yeah, that seems as reasonable as any other approach I might come up with, but I'd make it a lot more robust. No open tasks on a row before it can be edited, etc etc.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply