@@ -47,7 +47,7 @@ problems and is very inconvenient.
4747This declaration creates a relationship between two (or even more) tables.
4848
4949Foreign key (FK)
50- ===========
50+ ================
5151
5252So far, you have knowledge about **primary** keys.
5353The **foreign** key is a column, that *references* some another table.
@@ -71,7 +71,7 @@ that each record within a table has a matching one entity in another table.
7171This brings us to various relationship models.
7272
7373One-to-many relationship (1-to-N)
74- ------------------------
74+ ---------------------------------
7575
7676This is the most common relationship.
7777
@@ -102,7 +102,7 @@ But each employee can be physically located only in a single office at a time.
102102 }
103103
104104One-to-one relationship (1-to-1)
105- -----------------------
105+ --------------------------------
106106
107107``UNIQUE`` and ``NOT NULL`` constraints are used together to ensure there is
108108and only one matching record. Back to the example with employees. Multiple
@@ -115,7 +115,7 @@ The only one person can occupy the only one work station at a time.
115115 employee ||--|| work_station : occupies
116116
117117Many-to-many relationship (N-to-N)
118- -------------------------
118+ ----------------------------------
119119
120120These relationships require additional table.
121121A good example may be a *project role*. There are many of them in a production
0 commit comments