Question

I'm really trying to wrap my head around the concept of transforming EER Diagrams into relations. I understand that simple attributes must be mapped directly on the relation. My problem arises when dealing with composite and multivalued attributes. Do you create new relations for either one of them? For example, a customer entity may have a name, address, and postal code. The address attribute contains street, city, state, and address #. Does this mean that a new relation should be created or all component attributes should be listed in the customer relation? And lastly how is a multivalued attribute properly mapped, in easy to understand terms with an example?

Thanks for any help.

No correct solution

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top