You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto-generated via `{sandpaper}`
Source : 54083a9
Branch : main
Author : James Foster <38274066+jd-foster@users.noreply.github.com>
Time : 2026-04-30 01:51:14 +0000
Message : Discuss the meaning of "relational". (#367)
* Discuss the concept of relational.
* Move explanatory text outside definition.
* Update to address comments
@@ -125,8 +125,14 @@ Using a relational database serves several purposes.
125
125
- This means there's no risk of accidentally changing data when you analyze it.
126
126
- If we get new data we can rerun the query.
127
127
- It's fast, even for large amounts of data.
128
-
- It improves quality control of data entry (type constraints and use of forms in MS Access, Filemaker, Oracle Application Express etc.)
129
-
- The concepts of relational database querying are core to understanding how to do similar things using programming languages such as R or Python.
128
+
- It improves quality control of data entry.
129
+
- Restrictions on what is valid data within a table can be enforced in different ways, such as
130
+
the use of data types, cross-references and other relationships between tables.
131
+
- The concepts used in querying relational databases help us understanding how to do similar things in other programming languages such as R or Python.
132
+
133
+
In many small datasets we have only a few tables and we don't have to think about too many cross-references, or *keys*, between tables.
134
+
Shared keys between tables becomes increasingly important as the volume and complexity of data grows.
135
+
One motivation for using relational databases is being able to organize data using keys that must consistently refer to other tables.
130
136
131
137
### Database Management Systems
132
138
@@ -176,8 +182,8 @@ To summarize:
176
182
- One field per type of information
177
183
- No redundant information
178
184
- Split into separate tables with one table per class of information
179
-
- Needs an identifier in common between tables – shared column - to
180
-
reconnect (known as a *foreign key*).
185
+
- Needs an identifier in common between tables – a shared column - to
186
+
reconnect the information (known as a *foreign key* constraint).
0 commit comments