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.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
|
Tip
To read more about one-to-many relations visit 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.
1 2 3 4 5 6 7 8 |
|
Tip
To read more about many-to-one relations (i.e changing the name of generated field) visit foreign-keys section
Tip
Reverse ForeignKey allows you to query the related models with 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.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
|
Tip
To read more about many-to-many relations visit many-to-many section
Tip
ManyToMany allows you to query the related models with 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.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
|
Tip
To read more about many-to-many relations and through fields visit many-to-many section
Tip
ManyToMany allows you to query the related models with 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 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:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
|
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.
1 2 3 4 5 6 7 8 9 10 11 12 |
|
Tip
To read more about self-reference and postponed relations visit postponed-annotations section