- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 23 for store (5.42 sec)
-
docs/en/docs/tutorial/response-model.md
But if we use the same model for another *path operation*, we could be sending our user's passwords to every client. !!! danger Never store the plain password of a user or send it in a response like this, unless you know all the caveats and you know what you are doing. ## Add an output model
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 17.9K bytes - Viewed (0) -
docs/en/docs/alternatives.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23.2K bytes - Viewed (0) -
docs/en/docs/tutorial/extra-models.md
* The **input model** needs to be able to have a password. * The **output model** should not have a password. * The **database model** would probably need to have a hashed password. !!! danger Never store user's plaintext passwords. Always store a "secure hash" that you can then verify. If you don't know, you will learn what a "password hash" is in the [security chapters](security/simple-oauth2.md#password-hashing){.internal-link target=_blank}.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.7K bytes - Viewed (1) -
docs/en/docs/async.md
The fast food store has 8 processors (cashiers/cooks). While the concurrent burgers store might have had only 2 (one cashier and one cook). But still, the final experience is not the best. 😞 --- This would be the parallel equivalent story for burgers. 🍔 For a more "real life" example of this, imagine a bank.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23K bytes - Viewed (0) -
docs/zh/docs/tutorial/body-updates.md
然后再用它生成一个只含已设置(在请求中所发送)数据,且省略了默认值的 `dict`: ```Python hl_lines="34" {!../../../docs_src/body_updates/tutorial002.py!} ``` ### 使用 Pydantic 的 `update` 参数 接下来,用 `.copy()` 为已有模型创建调用 `update` 参数的副本,该参数为包含更新数据的 `dict`。 例如,`stored_item_model.copy(update=update_data)`: ```Python hl_lines="35" {!../../../docs_src/body_updates/tutorial002.py!} ``` ### 更新部分数据小结 简而言之,更新部分数据应: * 使用 `PATCH` 而不是 `PUT` (可选,也可以用 `PUT`); * 提取存储的数据;
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 3.6K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/index.md
```Python commons: Annotated[dict, Depends(common_parameters)] ``` But because we are using `Annotated`, we can store that `Annotated` value in a variable and use it in multiple places: === "Python 3.10+" ```Python hl_lines="12 16 21" {!> ../../../docs_src/dependencies/tutorial001_02_an_py310.py!} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.6K bytes - Viewed (0) -
docs/en/docs/how-to/sql-databases-peewee.md
```Python hl_lines="18-20" {!../../../docs_src/sql_databases_peewee/sql_app/main.py!} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 16 13:23:25 GMT 2024 - 23.6K bytes - Viewed (1) -
docs/en/docs/how-to/nosql-databases-couchbase.md
``` We will use this model in our *path operation function*, so, we don't include in it the `hashed_password`. ### `UserInDB` model Now, let's create a `UserInDB` model. This will have the data that is actually stored in the database. We don't create it as a subclass of Pydantic's `BaseModel` but as a subclass of our own `User`, because it will have all the attributes in `User` plus a couple more: ```Python hl_lines="31-33"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 16 13:23:25 GMT 2024 - 6K bytes - Viewed (0) -
docs/em/docs/advanced/settings.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 11.4K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
* So, the user will have to log in again at some point later. * And if the token is stolen, the risk is less. It is not like a permanent key that will work forever (in most of the cases). * The frontend stores that token temporarily somewhere. * The user clicks in the frontend to go to another section of the frontend web app. * The frontend needs to fetch some more data from the API.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 8.9K bytes - Viewed (0)