From 1263024be557e0024cb4b6f8565b53ab8359cecf Mon Sep 17 00:00:00 2001 From: Lucien O <36520137+luco17@users.noreply.github.com> Date: Wed, 5 Jun 2024 01:00:14 +0100 Subject: [PATCH] =?utf8?q?=E2=9C=8F=EF=B8=8F=20Fix=20typo=20in=20`docs/tut?= =?utf8?q?orial`=20(#943)?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit --- docs/tutorial/create-db-and-table.md | 4 ++-- docs/tutorial/indexes.md | 2 +- docs/tutorial/select.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/tutorial/create-db-and-table.md b/docs/tutorial/create-db-and-table.md index d87b935a..f508cf7c 100644 --- a/docs/tutorial/create-db-and-table.md +++ b/docs/tutorial/create-db-and-table.md @@ -354,7 +354,7 @@ But we will talk about it later. ### Engine Database URL -Each supported database has it's own URL type. For example, for **SQLite** it is `sqlite:///` followed by the file path. For example: +Each supported database has its own URL type. For example, for **SQLite** it is `sqlite:///` followed by the file path. For example: * `sqlite:///database.db` * `sqlite:///databases/local/application.db` @@ -470,7 +470,7 @@ If you didn't know about SQLAlchemy before and are just learning **SQLModel**, y You can read a lot more about the engine in the SQLAlchemy documentation. -**SQLModel** defines it's own `create_engine()` function. It is the same as SQLAlchemy's `create_engine()`, but with the difference that it defaults to use `future=True` (which means that it uses the style of the latest SQLAlchemy, 1.4, and the future 2.0). +**SQLModel** defines its own `create_engine()` function. It is the same as SQLAlchemy's `create_engine()`, but with the difference that it defaults to use `future=True` (which means that it uses the style of the latest SQLAlchemy, 1.4, and the future 2.0). And SQLModel's version of `create_engine()` is type annotated internally, so your editor will be able to help you with autocompletion and inline errors. diff --git a/docs/tutorial/indexes.md b/docs/tutorial/indexes.md index d0854720..d0724f51 100644 --- a/docs/tutorial/indexes.md +++ b/docs/tutorial/indexes.md @@ -90,7 +90,7 @@ Do you like **fancy words**? Cool! Programmers tend to like fancy words. 😅 That algorithm I showed you above is called **Binary Search**. -It's called like that because you **search** something by splitting the dictionary (or any ordered list of things) in **two** ("binary" means "two") parts. And you do that process multiple times until you find what you want. +It's called that because you **search** something by splitting the dictionary (or any ordered list of things) in **two** ("binary" means "two") parts. And you do that process multiple times until you find what you want. /// diff --git a/docs/tutorial/select.md b/docs/tutorial/select.md index 47c80a26..be66de35 100644 --- a/docs/tutorial/select.md +++ b/docs/tutorial/select.md @@ -713,7 +713,7 @@ In this chapter we are touching some of them. When importing from `sqlmodel` the `select()` function, you are using **SQLModel**'s version of `select`. -SQLAchemy also has it's own `select`, and SQLModel's `select` uses SQLAlchemy's `select` internally. +SQLAchemy also has its own `select`, and SQLModel's `select` uses SQLAlchemy's `select` internally. But SQLModel's version does a lot of **tricks** with type annotations to make sure you get the best **editor support** possible, no matter if you use **VS Code**, **PyCharm**, or something else. ✨ -- 2.47.2