PaiGramTeam/sqlmodel
3
0
Fork 0
mirror of https://github.com/PaiGramTeam/sqlmodel.git synced 2024-11-26 01:41:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

✏ Fix typos in docs/tutorial/fastapi/update.md (#268)

Browse Source 
Co-authored-by: Sebastián Ramírez <tiangolo@gmail.com>
This commit is contained in:
cirrusj 2022-08-28 00:00:09 +03:00 committed by GitHub
parent 04b8b3eedf
commit 452f18d8bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tutorial/fastapi/update.md
View File

@ -218,11 +218,11 @@ And when getting the data with `hero.dict(exclude_unset=True)`, we would get:
} }
``` ```
So, we would use that value and upate the `age` to `None` in the database, **just as the client intended**. So, we would use that value and update the `age` to `None` in the database, **just as the client intended**.
Notice that `age` here is `None`, and **we still detected it**. Notice that `age` here is `None`, and **we still detected it**.
Also that `name` was not even sent, and we don't *accidentally* set it to `None` or something, we just didn't touch it, because the client didn't send it, so we are **perfectly fine**, even in these corner cases. ✨ Also that `name` was not even sent, and we don't *accidentally* set it to `None` or something, we just didn't touch it, because the client didn't sent it, so we are **perfectly fine**, even in these corner cases. ✨
These are some of the advantages of Pydantic, that we can use with SQLModel. 🎉 These are some of the advantages of Pydantic, that we can use with SQLModel. 🎉