Mapping Specialization/Generalization,”SUPERTYPE(CommonIdent, CommonAttr1, CommonAttr2)SUBTYPE1(CommonIdent, UniqueAttr1)SUBTYPE2(CommonIdent, UniqueAttr2, UniqueAttr3)As an alternative mapping for total specialization with disjoint relations, you can may consider dropping the supertype and creating tables for each subtype:SUBTYPE1(CommonIdent, CommonAttr1, CommonAttr2, UniqueAttr1)SUBTYPE2(CommonIdent, CommonAttr1, CommonAttr2, UniqueAttr2, UniqueAttr3)SUBTYPE3(CommonIdent, CommonAttr1, CommonAttr2

Average Rating 0 out of 5 stars. 0 votes.You must log in to submit a review.Mapping Specialization/Generalization,”SUPERTYPE(CommonIdent, CommonAttr1, CommonAttr2)SUBTYPE1(CommonIdent, UniqueAttr1)SUBTYPE2(CommonIdent,[…]

Read more

Miscellaneous issues 1,”For composite attributes, include only the atomic attributes:CUSTOMER(CustID, Age, Street, City, State, Zip)For a composite attribute that serves as a primary key, you would need to underline all sub-attributes in the relation to clarify this (e.g., for a composite primary key such as FullName, this may break down into: FirstName, MiddleName

Average Rating 0 out of 5 stars. 0 votes.You must log in to submit a review.Miscellaneous issues 1,”For composite attributes,[…]

Read more