
In many ways, the Entity Relationship Diagram (ERD) describes the operations in table and field terms. As experienced, gnarly developers, we can say for sure your initial instincts are often wrong.ĭatabase relationships reflect the operations of the underlying organization. It’s easy to jump to a conclusion based on one’s perception of how a business operates.

Those new to database design often have a preconceived notion of what type of relationship fits a pair of entities. In this article, we’ll cover one-to-one and many-to-many database relationships. Other types of relationships occur as well. When the child’s foreign key value matches the parent’s primary key value we have a link between those records. A child record displays part of the DNA of its parent by carrying the unique parent ID in a foreign key field. A parent record has a primary key that is assigned when a record is created. Those relationships are defined through data. A parent record can have many child records, but a child record belongs to one and only one parent record.

By far, this is the most common type of data relationship that we encounter. Previously, we discussed one-to-many relational databases.
