✏ Fix typos in docs/tutorial/index.md
and docs/databases.md
(#5)
Co-authored-by: Sebastián Ramírez <tiangolo@gmail.com>
This commit is contained in:
parent
02697459b8
commit
32b5b39f2d
@ -250,7 +250,7 @@ As these **primary key** IDs can uniquely identify each row on the table for tea
|
|||||||
|
|
||||||
<img alt="table relationships" src="/img/databases/relationships.svg">
|
<img alt="table relationships" src="/img/databases/relationships.svg">
|
||||||
|
|
||||||
So, in the table for heroes, we use the `team_id` column to define a relationship to the *foreign* table for teams. Each value in the `team_id` column on the table with heroes will be the same value as the `id` column of one row in the table wiwth teams.
|
So, in the table for heroes, we use the `team_id` column to define a relationship to the *foreign* table for teams. Each value in the `team_id` column on the table with heroes will be the same value as the `id` column of one row in the table with teams.
|
||||||
|
|
||||||
In the table for heroes we have a **primary key** that is the `id`. But we also have another column `team_id` that refers to a **key** in a **foreign** table. There's a technical term for that too, the `team_id` is a "**foreign key**".
|
In the table for heroes we have a **primary key** that is the `id`. But we also have another column `team_id` that refers to a **key** in a **foreign** table. There's a technical term for that too, the `team_id` is a "**foreign key**".
|
||||||
|
|
||||||
|
@ -97,7 +97,7 @@ $ python3 --version
|
|||||||
// This is too old! 😱
|
// This is too old! 😱
|
||||||
Python 3.5.6
|
Python 3.5.6
|
||||||
// Let's see if python3.10 is available
|
// Let's see if python3.10 is available
|
||||||
$ python3.10 --verson
|
$ python3.10 --version
|
||||||
// Oh, no, this one is not available 😔
|
// Oh, no, this one is not available 😔
|
||||||
command not found: python3.10
|
command not found: python3.10
|
||||||
$ python3.9 --version
|
$ python3.9 --version
|
||||||
|
Loading…
x
Reference in New Issue
Block a user