Skip to content
This repository was archived by the owner on Jul 2, 2024. It is now read-only.

Commit a41ee0b

Browse files
committed
Fixed headers
1 parent b2d178a commit a41ee0b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/rdbms/relations.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ problems and is very inconvenient.
4747
This declaration creates a relationship between two (or even more) tables.
4848

4949
Foreign key (FK)
50-
===========
50+
================
5151

5252
So far, you have knowledge about **primary** keys.
5353
The **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.
7171
This brings us to various relationship models.
7272

7373
One-to-many relationship (1-to-N)
74-
------------------------
74+
---------------------------------
7575

7676
This 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

104104
One-to-one relationship (1-to-1)
105-
-----------------------
105+
--------------------------------
106106

107107
``UNIQUE`` and ``NOT NULL`` constraints are used together to ensure there is
108108
and 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

117117
Many-to-many relationship (N-to-N)
118-
-------------------------
118+
----------------------------------
119119

120120
These relationships require additional table.
121121
A good example may be a *project role*. There are many of them in a production

0 commit comments

Comments
 (0)