Timeline for EER Diagram - subclasses which are neither disjoint nor fully overlapping
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2019 at 17:34 | vote | accept | knrumsey | ||
| Feb 18, 2019 at 19:28 | history | edited | ypercubeᵀᴹ | CC BY-SA 4.0 |
added 214 characters in body
|
| Feb 18, 2019 at 17:41 | comment | added | MDCCL | @knrumsey IMO, one of the most important points of this answer is the identification of the Service Request entity type (that appears to be overlooked so far), which associates the entity types named, say, Person and Service (which seems to have two different subtypes). The problem with your question is that it lacks several important details, so it entails several assumptions (which would have been avoided if the question was more complete). OTOH, a database designer should not "make" (or invent) subclasses, they should be discovered, delimited and represented properly, instead. | |
| Feb 18, 2019 at 17:23 | comment | added | knrumsey | So each service type has a large number of attributes specific to the service. This is why I wanted to make them subclasses. If I understand correctly, you are suggesting just one entity with all of the attributes for each service? Where all of the service_b attributes are optional? | |
| Feb 18, 2019 at 16:39 | history | edited | ypercubeᵀᴹ | CC BY-SA 4.0 |
added 38 characters in body
|
| Feb 18, 2019 at 16:31 | history | answered | ypercubeᵀᴹ | CC BY-SA 4.0 |