chenlong85.2004 schrieb: > could you help mei to explain the structure of workflow database > table structure?
The following tables hold workflow specifications: - Table "workflow" When a new workflow is defined, a new row is inserted into the "workflow" table. The "workflow_id" is automatically assigned (AUTO_INCREMENT) and the "workflow_version" is set to "1". When an existing workflow is changed, a new row is inserted into the "workflow" table. The "workflow_id" is automatically assigned (AUTO_INCREMENT) and the "workflow_version" is incremented. The "workflow_version_is_latest" column serves as a flag for efficiently fetching the latest version of a workflow. - Table "node" When a new workflow is defined, a new row is inserted into the "node" table for every node of the workflow's graph. When an existing workflow is changed, a new row is inserted into the "node" table for every node of the workflow's graph. - Table "node_connection" The "node_connection" table connects the nodes from the "node" table. - Table "variable_handler" The "variable_handler" table stores the information about the variable handlers of a workflow. The following tables are used at workflow runtime: - Table "execution" When the execution of a workflow is started, a new row is inserted into the "execution" table. When the execution of a workflow is ended, the corresponding rows are deleted from the "execution" and "execution_state" tables. - Table "execution_state" When the execution of a workflow is suspended, a new row is inserted into the "execution_state" table for each node of the workflow that is activated at the time. When the execution of a workflow is resumed, the corresponding rows are deleted from the "execution_state" table. -- Sebastian Bergmann System Developer s...@ez.no | eZ Systems | http://ez.no
signature.asc
Description: OpenPGP digital signature
-- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components