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
Copy file name to clipboardExpand all lines: docs/databases.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,9 +99,9 @@ Having distributed systems also creates additional challenges, so there's a high
99
99
100
100
We already talked about the different ways to interact with a database and how they handle files, etc. That applies to most or all of the databases.
101
101
102
-
But there's another way to categorize databases that is very important. As you can imagine, there are many types of databases and many databases in each group. But in general, they can be separated in two big groups: **SQL** databases and **NoSQL** databases.
102
+
But there's another way to categorize databases that is very important. As you can imagine, there are many types of databases and many databases in each group. But in general, they can be separated in two big groups: "SQL Databases" and "NoSQL Databases".
103
103
104
-
We will get to why the name is "SQL" in a bit, but first, let's see what is it all about.
104
+
We will get to why the name "SQL" in a bit, but first, let's see what is it all about.
105
105
106
106
### SQLModel for SQL Databases
107
107
@@ -264,17 +264,17 @@ It doesn't have the meaning that you would use in English of something being rel
264
264
265
265
The technical term **relation** just refers to each one of these tables.
266
266
267
-
And because of this technical term, these **SQL Databases** are also called **Relational Databases** (in fact, that is the technically correct term). But it still just refers to these as databases made with multiple tables.
267
+
And because of this technical term, these **SQL Databases** are also called **Relational Databases** (in fact, that is the technically correct term). But it still just refers to these databases made with multiple tables.
268
268
269
269
### SQL - The Language
270
270
271
-
After developing these ideas of how to store data in multiple tables, the same smart people also created a **language** that could be used to interact with them.
271
+
After developing these ideas of how to store data in multiple tables they also created a **language** that could be used to interact with them.
272
272
273
-
The language is called **SQL**, which stands for **Structured Query Language**.
273
+
The language is called **SQL**, the name comes from for **Structured Query Language**.
274
274
275
-
Despite its name, the SQL language is not only used to *query* for data. It is also used to create records/rows, update them, delete them, manipulate the database, create tables, etc.
275
+
Nevertheless, the language is not only used to *query* for data. It is also used to create records/rows, to update them, to delete them. And to manipulate the database, create tables, etc.
276
276
277
-
Because this language is supported by all these databases that handle multiple tables, they are called **SQL Databases**. However, it's important to note that each database has small variations in the SQL language (*dialect*) they support.
277
+
This language is supported by all these databases that handle multiple tables, that's why they are called **SQL Databases**. Although, each database has small variations in the SQL language they support (*dialect*).
278
278
279
279
Let's imagine that the table holding the heroes is called the `hero` table. An example of a SQL query to get all the data from it could look like:
0 commit comments