From: berkaykrc Date: Mon, 9 Mar 2026 09:37:33 +0000 (+0300) Subject: 📝 Fix ambiguous phrasing regarding `HeroPublicWithTeam` model (#1678) X-Git-Tag: 0.0.38~42 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d97fef4a22600c726e04d70927b4d34338d4ba85;p=thirdparty%2Ffastapi%2Fsqlmodel.git 📝 Fix ambiguous phrasing regarding `HeroPublicWithTeam` model (#1678) * docs: Fix ambiguous phrasing regarding HeroPublicWithTeam model * apply suggestion from Yurii --------- Co-authored-by: Sofie Van Landeghem Co-authored-by: svlandeg --- diff --git a/docs/tutorial/fastapi/relationships.md b/docs/tutorial/fastapi/relationships.md index f789fd930..8c69b5177 100644 --- a/docs/tutorial/fastapi/relationships.md +++ b/docs/tutorial/fastapi/relationships.md @@ -146,13 +146,13 @@ Then we do the same for the `TeamPublicWithHeroes`, it **inherits** from `TeamPu ### Data Models Without Relationship Attributes -Now, notice that these new fields `team` and `heroes` are not declared with `Relationship()`, because these are not **table models**, they cannot have **relationship attributes** with the magic access to get that data from the database. +Now, notice that these new fields `team` and `heroes` are not declared with `Relationship()`, because `HeroPublicWithTeam` and `TeamPublicWithHeroes` are not **table models**, they cannot have **relationship attributes** with the magic access to get that data from the database. Instead, here these are only **data models** that will tell FastAPI **which attributes** to get data from and **which data** to get from them. ### Reference to Other Models -Also, notice that the field `team` is not declared with this new `TeamPublicWithHeroes`, because that would again create that infinite recursion of data. Instead, we declare it with the normal `TeamPublic` model. +Also, notice that in the `HeroPublicWithTeam` model, the field `team` is not declared with this new `TeamPublicWithHeroes`, because that would again create that infinite recursion of data. Instead, we declare it with the normal `TeamPublic` model. And the same for `TeamPublicWithHeroes`, the model used for the new field `heroes` uses `HeroPublic` to get only each hero's data.