Online College Courses for Credit

+
Weak Relationships and Entities

Weak Relationships and Entities

Rating:
(0)
Author: Sophia Tutorial
Description:

Identify weak relationships and entities.

(more)
See More
Fast, Free College Credit

Developing Effective Teams

Let's Ride
*No strings attached. This college course is 100% free and is worth 1 semester credit.

47 Sophia partners guarantee credit transfer.

299 Institutions have accepted or given pre-approval for credit transfer.

* The American Council on Education's College Credit Recommendation Service (ACE Credit®) has evaluated and recommended college credit for 33 of Sophia’s online courses. Many different colleges and universities consider ACE CREDIT recommendations in determining the applicability to their course and degree programs.

Tutorial

what's covered
This tutorial explores the weak relationships and entities in ERDs.

The relationship strength is important to determine how the primary key of a related identity is defined. There are instances where the primary key of one entity only appears as the foreign key in the related entity, in those cases, we have a weak relationship. There are other times where the foreign key is also the primary key component in the related entity which creates a strong relationship. With Chen’s notation, it does not distinguish in a diagram of the difference between a weak and strong relationship. In Crow’s foot notation, a dashed relationship line is used to signify a weak relationship. This is not always used in diagraming ERDs. However, it is useful to know this if you do see it in a diagram.

The other aspect to consider in ERDs is strong and weak entities. A strong entity can exist without any dependency on any other relationship. Typically, these entities are ones that do not have any foreign keys. These tables are the ones that you would typically create first since they don’t depend on other entities. Other entities will typically depend on them. Weak entities are ones that meet one of two criteria. The first criterion that would define a weak entity is if it is existence-dependent. This means that it cannot exists without the entity that it has a relationship with. The other criteria of a weak entity are if the entity has a primary key that is partially or entirely derived from the parent entity in the relationship. This means that if there is a strong relationship, the entity that derives from the other table is a weak entity.

In Crow’s foot notation, the relationship line along with the primary key/foreign key is used to signify the weak entity. In Chen’s notation, the weak entity is defined by a double wall on the entity. This would be the case for the Rating entity in our current design. We have not normalized the database yet to create the bridge entity between movie/actor and movie/genre but those bridge entities would also be weak entities. The Rating entity will have dependencies on both the user and the movie. A rating cannot exist without having the user that submitted the rating. A rating cannot exist without being connected to a movie either.

File:11524-5130-1.png


summary
Weak relationships and weak entities will help to signify the relationship strength between a set of entities.