✏️ Fix typos found with codespell (#520)
Found via `codespell -S *.svg,*.css,*.js,*.drawio -L pullrequest,sesion`
This commit is contained in:
@@ -190,7 +190,7 @@ First we have to import `select` from `sqlmodel` at the top of the file:
|
||||
```Python hl_lines="3"
|
||||
{!./docs_src/tutorial/select/tutorial001.py[ln:1-3]!}
|
||||
|
||||
# More code below ommitted 👇
|
||||
# More code below omitted 👇
|
||||
```
|
||||
|
||||
<details>
|
||||
@@ -472,7 +472,7 @@ SQLAlchemy's own `Session` has a method `session.execute()`. It doesn't have a `
|
||||
|
||||
If you see SQLAlchemy tutorials, they will always use `session.execute()`.
|
||||
|
||||
**SQLModel**'s own `Session` inherits directly from SQLAlchemy's `Session`, and adds this additonal method `session.exec()`. Underneath, it uses the same `session.execute()`.
|
||||
**SQLModel**'s own `Session` inherits directly from SQLAlchemy's `Session`, and adds this additional method `session.exec()`. Underneath, it uses the same `session.execute()`.
|
||||
|
||||
But `session.exec()` does several **tricks** combined with the tricks in `session()` to give you the **best editor support**, with **autocompletion** and **inline errors** everywhere, even after getting data from a select. ✨
|
||||
|
||||
|
||||
Reference in New Issue
Block a user