* WIP * WIP - make test_model_definition tests pass * WIP - make test_model_methods pass * WIP - make whole test suit at least run - failing 49/443 tests * WIP fix part of the getting pydantic tests as types of fields are now kept in core schema and not on fieldsinfo * WIP fix validation in update by creating individual fields validators, failing 36/443 * WIP fix __pydantic_extra__ in intializing model, fix test related to pydantic config checks, failing 32/442 * WIP - fix enum schema in model_json_schema, failing 31/442 * WIP - fix copying through model, fix setting pydantic fields on through, fix default config and inheriting from it, failing 26/442 * WIP fix tests checking pydantic schema, fix excluding parent fields, failing 21/442 * WIP some missed files * WIP - fix validators inheritance and fix validators in generated pydantic, failing 17/442 * WIP - fix through models setting - only on reverse side of relation, but always on reverse side, failing 15/442 * WIP - fix through models setting - only on reverse side of relation, but always on reverse side, failing 15/442 * WIP - working on proper populating __dict__ for relations for new schema dumping, some work on openapi docs, failing 13/442 * WIP - remove property fields as pydantic has now computed_field on its own, failing 9/442 * WIP - fixes in docs, failing 8/442 * WIP - fix tests for largebinary schema, wrapped bytes fields fail in pydantic, will be fixed in pydantic-core, remaining is circural schema for related models, failing 6/442 * WIP - fix to pk only models in schemas * Getting test suites to pass (#1249) * wip, fixing tests * iteration, fixing some more tests * iteration, fixing some more tests * adhere to comments * adhere to comments * remove unnecessary dict call, re-add getattribute for testing * todo for reverse relationship * adhere to comments, remove prints * solve circular refs * all tests pass 🎉 * remove 3.7 from tests * add lint and type check jobs * reforat with ruff, fix jobs * rename jobs * fix imports * fix evaluate in py3.8 * partially fix coverage * fix coverage, add more tests * fix test ids * fix test ids * fix lint, fix docs, make docs fully working scripts, add test docs job * fix pyproject * pin py ver in test docs * change dir in test docs * fix pydantic warning hack * rm poetry call in test_docs * switch to pathlib in test docs * remove coverage req test docs * fix type check tests, fix part of types * fix/skip next part of types * fix next part of types * fix next part of types * fix coverage * fix coverage * fix type (bit dirty 🤷) * fix some code smells * change pre-commit * tweak workflows * remove no root from tests * switch to full python path by passing sys.executable * some small refactor in new base model, one sample test, change makefile * small refactors to reduce complexity of methods * temp add tests for prs against pydantic_v2 * remove all references to __fields__ * remove all references to construct, deprecate the method and update model_construct to be in line with pydantic * deprecate dict and add model_dump, todo switch to model_dict in calls * fix tests * change to union * change to union * change to model_dump and model_dump_json from dict and json deprecated methods, deprecate them in ormar too * finish switching dict() -> model_dump() * finish switching json() -> model_dump_json() * remove fully pydantic_only * switch to extra for payment card, change missed json calls * fix coverage - no more warnings internal * fix coverage - no more warnings internal - part 2 * split model_construct into own and pydantic parts * split determine pydantic field type * change to new field validators * fix benchmarks, add codspeed instead of pytest-benchmark, add action and gh workflow * restore pytest-benchmark * remove codspeed * pin pydantic version, restore codspeed * change on push to pydantic_v2 to trigger first one * Use lifespan function instead of event (#1259) * check return types * fix imports order, set warnings=False on json that passes the dict, fix unnecessary loop in one of the test * remove references to model's meta as it's now ormar config, rename related methods too * filter out pydantic serializer warnings * remove choices leftovers * remove leftovers after property_fields, keep only enough to exclude them in initialization * add migration guide * fix meta references * downgrade databases for now * Change line numbers in documentation (#1265) * proofread and fix the docs, part 1 * proofread and fix the docs for models * proofread and fix the docs for fields * proofread and fix the docs for relations * proofread and fix rest of the docs, add release notes for 0.20 * create tables in new docs src * cleanup old deps, uncomment docs publish on tag * fix import reorder --------- Co-authored-by: TouwaStar <30479449+TouwaStar@users.noreply.github.com> Co-authored-by: Goran Mekić <meka@tilda.center>
218 lines
6.6 KiB
Markdown
218 lines
6.6 KiB
Markdown
# Relations
|
|
|
|
Currently `ormar` supports two types of relations:
|
|
|
|
* One-to-many (and many-to-one) with `ForeignKey` field
|
|
* Many-to-many with `ManyToMany` field
|
|
|
|
Below you can find a very basic examples of definitions for each of those relations.
|
|
|
|
To read more about methods, possibilities, definition etc. please read the subsequent section of the documentation.
|
|
|
|
## ForeignKey
|
|
|
|
To define many-to-one relation use `ForeignKey` field.
|
|
|
|
```Python hl_lines="26"
|
|
--8<-- "../docs_src/relations/docs003.py"
|
|
```
|
|
|
|
!!!tip
|
|
To read more about one-to-many relations visit [foreign-keys][foreign-keys] section
|
|
|
|
## Reverse ForeignKey
|
|
|
|
The definition of one-to-many relation also uses `ForeignKey`, and it's registered for you automatically.
|
|
|
|
So in relation to example above.
|
|
|
|
```Python hl_lines="7-8"
|
|
class Department(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
# there is a virtual field here like follows
|
|
courses: Optional[List[Course]] = ormar.ForeignKey(Course, virtual=True)
|
|
# note that you DO NOT define it yourself, ormar does it for you.
|
|
```
|
|
|
|
!!!tip
|
|
To read more about many-to-one relations (i.e changing the name of generated field) visit [foreign-keys][foreign-keys] section
|
|
|
|
|
|
!!!tip
|
|
Reverse ForeignKey allows you to query the related models with [queryset-proxy][queryset-proxy].
|
|
|
|
It allows you to use `await department.courses.all()` to fetch data related only to specific department etc.
|
|
|
|
##ManyToMany
|
|
|
|
To define many-to-many relation use `ManyToMany` field.
|
|
|
|
```python hl_lines="19"
|
|
class Category(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
tablename="categories",
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=40)
|
|
|
|
class Post(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
title: str = ormar.String(max_length=200)
|
|
categories: Optional[List[Category]] = ormar.ManyToMany(Category)
|
|
```
|
|
|
|
|
|
!!!tip
|
|
To read more about many-to-many relations visit [many-to-many][many-to-many] section
|
|
|
|
|
|
!!!tip
|
|
ManyToMany allows you to query the related models with [queryset-proxy][queryset-proxy].
|
|
|
|
It allows you to use `await post.categories.all()` but also `await category.posts.all()` to fetch data related only to specific post, category etc.
|
|
|
|
## Through fields
|
|
|
|
As part of the `ManyToMany` relation you can define a through model, that can contain additional
|
|
fields that you can use to filter, order etc. Fields defined like this are exposed on the reverse
|
|
side of the current query for m2m models.
|
|
|
|
So if you query from model `A` to model `B`, only model `B` has through field exposed.
|
|
Which kind of make sense, since it's a one through model/field for each of related models.
|
|
|
|
```python hl_lines="12-21"
|
|
class Category(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
tablename="categories",
|
|
)
|
|
|
|
id = ormar.Integer(primary_key=True)
|
|
name = ormar.String(max_length=40)
|
|
|
|
# you can specify additional fields on through model
|
|
class PostCategory(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
tablename="posts_x_categories",
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
sort_order: int = ormar.Integer(nullable=True)
|
|
param_name: str = ormar.String(default="Name", max_length=200)
|
|
|
|
|
|
class Post(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
title: str = ormar.String(max_length=200)
|
|
categories = ormar.ManyToMany(Category, through=PostCategory)
|
|
```
|
|
|
|
!!!tip
|
|
To read more about many-to-many relations and through fields visit [many-to-many][many-to-many] section
|
|
|
|
|
|
!!!tip
|
|
ManyToMany allows you to query the related models with [queryset-proxy][queryset-proxy].
|
|
|
|
It allows you to use `await post.categories.all()` but also `await category.posts.all()` to fetch data related only to specific post, category etc.
|
|
|
|
## Relationship default sort order
|
|
|
|
By default relations follow model default sort order so `primary_key` column ascending, or any sort order se in `ormar_config` object.
|
|
|
|
!!!tip
|
|
To read more about models sort order visit [models](../models/index.md#model-sort-order) section of documentation
|
|
|
|
But you can modify the order in which related models are loaded during query by providing `orders_by` and `related_orders_by`
|
|
parameters to relations.
|
|
|
|
In relations you can sort only by directly related model columns or for `ManyToMany`
|
|
columns also `Through` model columns `{through_field_name}__{column_name}`
|
|
|
|
Sample configuration might look like this:
|
|
|
|
```python hl_lines="23"
|
|
database = databases.Database(DATABASE_URL)
|
|
metadata = sqlalchemy.MetaData()
|
|
|
|
|
|
base_ormar_config = ormar.OrmarConfig(
|
|
database=database,
|
|
metadata=metadata,
|
|
)
|
|
|
|
|
|
class Author(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
|
|
|
|
class Book(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
author: Optional[Author] = ormar.ForeignKey(
|
|
Author, orders_by=["name"], related_orders_by=["-year"]
|
|
)
|
|
title: str = ormar.String(max_length=100)
|
|
year: int = ormar.Integer(nullable=True)
|
|
ranking: int = ormar.Integer(nullable=True)
|
|
```
|
|
|
|
Now calls:
|
|
|
|
`await Author.objects.select_related("books").get()` - the books will be sorted by the book year descending
|
|
|
|
`await Book.objects.select_related("author").all()` - the authors will be sorted by author name ascending
|
|
|
|
## Self-reference and postponed references
|
|
|
|
In order to create auto-relation or create two models that reference each other in at least two
|
|
different relations (remember the reverse side is auto-registered for you), you need to use
|
|
`ForwardRef` from `typing` module.
|
|
|
|
```python hl_lines="1 9 12"
|
|
PersonRef = ForwardRef("Person")
|
|
|
|
|
|
class Person(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
supervisor: PersonRef = ormar.ForeignKey(PersonRef, related_name="employees")
|
|
|
|
|
|
Person.update_forward_refs()
|
|
```
|
|
|
|
!!!tip
|
|
To read more about self-reference and postponed relations visit [postponed-annotations][postponed-annotations] section
|
|
|
|
|
|
[foreign-keys]: ./foreign-key.md
|
|
[many-to-many]: ./many-to-many.md
|
|
[queryset-proxy]: ./queryset-proxy.md
|
|
[postponed-annotations]: ./postponed-annotations.md
|