Database table design issue

Scenario: There is a hierarchy PROCESS. how

PR-2, PR-3 are children of Pr-1,

PR-4, PR-5 are children of PR-2

leaf processes (in our case PR-3, PR-4 and PR-5Can now be described in terms of seriesACTIVITY

Now it ACTIVITYis just a child PROCESS, but has some additional attributes, therefore

Should I make two diff. tables in the database (one for ACTIVITYand one for PROCESS)?

or

Should I add some fields (for additional attributes ACTIVITIY) in the table PROCESSand save the table ACTIVITYin PROCESS.

=================================================== ================================================ ==== =========================

Actually, here PROCESSAND ACTIVITYis the one that is involved in BPM (Busineses process management)

Those with BPM knowledge can find out that ACTIVITYAND PROCESS.

Those who do not know BPM, I explain to you what I mean by PROCESSand ACTIVITY.

Any enterprise has various PROCESSes (for example, CustomerOrderPlaced, CustomerOrderCancelled, etc.) and ACTIVITies are parts of the process that must be completed to complete the process.

So, ACTIVITYis a child PROCESSwith some additional attributes.

Or from a Java perspective, ACTIVITY extends PROCESS

+1
source share
2 answers

: "ACTIVITY ", "ACTIVITY extends PROCESS" . . .

ER " " . , , " ", .

, CustomerPlacesOrder - . :

  • ;
  • ,
  • , ;
  • ;
  • , ;
  • .

. .

+1

. :

ProcessTable

ID ( )
ProcessName
ProcessCode...

ActivityTable

ID ( )
ActivityName
ActivityCode
ActivityDesc
ProcessID ( )...

0

Source: https://habr.com/ru/post/1733655/


All Articles