Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The schema for workflows is greatly affected by whether your workflows have branching or not. If all of your workflows are linear with no branching, the problem is much simpler, because the definition of a workflow configuration need only list the steps in the workflow, and a document workflow instance only needs to record the current step. If conditional branching or parallel steps are involved, you need to use some sort of hierarchical model for the steps (eg each workflow configuration step could have a pointer to parents and pointer to children). These are often stored in XML.</p> <p>The simple case with no branching can look like this:</p> <p>table: workflow_config (one row per workflow)</p> <ul> <li>workflow_config_id </li> <li>name</li> <li>description</li> </ul> <p>table: workflow_config_step (one row for each workflow step)</p> <ul> <li>workflow_config_id</li> <li>step_id</li> <li>name</li> <li>description</li> <li>action_id</li> <li>parameters (or context, or whatever information needs to be passed to the action launcher)</li> </ul> <p>table: document_workflow (one row for each document)</p> <ul> <li>document_id</li> <li>workflow_id</li> <li>current_step_id</li> <li>parameters (or context, or whatever information needs to be passed from one step to the next)</li> </ul> <p>table: document_workflow_step (one row for each action taken on the document)</p> <ul> <li>document_id</li> <li>step_id</li> <li>status</li> <li>timestamp</li> </ul> <p>Note that branching workflows need to carry much more information from stage to stage. In fact the "parameters" attribute may need to be in a separate crosslinked table. I'm only calling it a field here because you may use delimited or XML representation if very little data is needed.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat database structure for a document management system?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdj_segfault
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat database structure for a document management system?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for ur reply. What must be the structure if i want to use the branching without XML. We just need to save all the workflow in database instead of XML.
      singulars
      1. PO
      1. USvikas27
    2. COWell, a database field can hold XML, so they're not mutually exclusive. If you need simple parallelism (multiple steps running at the same time), you can use a non-unique step number, and have the workflow fire up each workflow process at the same step at the same time, and not go on to the next step number until all processes at the current step have finished. If you need conditional branching, it all depends on how complex the conditionals are, and whether all conditions are binary or trinary or poly.
      singulars
      1. PO
      1. USdj_segfault
    3. COAs per our discussion and my understanding i make 4 tables. They are: DocumentTable[DocId][DocName][DocType][DocLocation][UploadedBy][DocStatus] PermissionTable[PerId][DocId][UserId][SequenceNo]SubSequenceNo] CurrentStatusTable[][StatusId][SequenceNo][DocId] And DocHistoryTable[DocHisId][DocId][UserId][Operation][Comment] . These are the tables i am using. So can u tell me if there is any kind of flaw in my structure. The operation is only Accept or Reject with comments.
      singulars
      1. PO
      1. USvikas27
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload