* 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>
144 lines
4.4 KiB
Markdown
144 lines
4.4 KiB
Markdown
# Postponed annotations
|
|
|
|
## Self-referencing Models
|
|
|
|
When you want to reference the same model during declaration to create a
|
|
relation you need to declare the referenced model as a `ForwardRef`, as during the declaration
|
|
the class is not yet ready and python by default won't let you reference it.
|
|
|
|
Although you might be tempted to use __future__ annotations or simply quote the name with `""` it won't work
|
|
as `ormar` is designed to work with explicitly declared `ForwardRef`.
|
|
|
|
First, you need to import the required ref from typing.
|
|
```python
|
|
from typing import ForwardRef
|
|
```
|
|
|
|
Now we need a sample model and a reference to the same model,
|
|
which will be used to create a self referencing relation.
|
|
|
|
```python
|
|
# create the forwardref to model Person
|
|
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)
|
|
# use the forwardref as to parameter
|
|
supervisor: PersonRef = ormar.ForeignKey(PersonRef, related_name="employees")
|
|
|
|
```
|
|
|
|
That's so simple. But before you can use the model you need to manually update the references
|
|
so that they lead to the actual models.
|
|
|
|
!!!warning
|
|
If you try to use the model without updated references, `ModelError` exception will be raised.
|
|
So in our example above any call like following will cause exception
|
|
```python
|
|
# creation of model - exception
|
|
await Person.objects.create(name="Test")
|
|
# initialization of model - exception
|
|
Person2(name="Test")
|
|
# usage of model's QuerySet - exception
|
|
await Person2.objects.get()
|
|
```
|
|
|
|
To update the references call the `update_forward_refs` method on **each model**
|
|
with forward references, only **after all related models were declared.**
|
|
|
|
So in order to make our previous example work we need just one extra line.
|
|
|
|
```python hl_lines="14"
|
|
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()
|
|
|
|
```
|
|
|
|
Of course the same can be done with ManyToMany relations in exactly same way, both for to
|
|
and through parameters.
|
|
|
|
```python
|
|
# declare the reference
|
|
ChildRef = ForwardRef("Child")
|
|
|
|
class ChildFriend(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
class Child(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
# use it in relation
|
|
friends = ormar.ManyToMany(ChildRef, through=ChildFriend,
|
|
related_name="also_friends")
|
|
|
|
|
|
Child.update_forward_refs()
|
|
```
|
|
|
|
## Cross model relations
|
|
|
|
The same mechanism and logic as for self-reference model can be used to link multiple different
|
|
models between each other.
|
|
|
|
Of course `ormar` links both sides of relation for you,
|
|
creating a reverse relation with specified (or default) `related_name`.
|
|
|
|
But if you need two (or more) relations between any two models, that for whatever reason
|
|
should be stored on both sides (so one relation is declared on one model,
|
|
and other on the second model), you need to use `ForwardRef` to achieve that.
|
|
|
|
Look at the following simple example.
|
|
|
|
```python
|
|
# teacher is not yet defined
|
|
TeacherRef = ForwardRef("Teacher")
|
|
|
|
|
|
class Student(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
# so we use reference instead of actual model
|
|
primary_teacher: TeacherRef = ormar.ForeignKey(TeacherRef,
|
|
related_name="own_students")
|
|
|
|
|
|
class StudentTeacher(ormar.Model):
|
|
ormar_config = base_ormar_config.copy(tablename='students_x_teachers')
|
|
|
|
|
|
class Teacher(ormar.Model):
|
|
ormar_config = base_ormar_config.copy()
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
name: str = ormar.String(max_length=100)
|
|
# we need students for other relation hence the order
|
|
students = ormar.ManyToMany(Student, through=StudentTeacher,
|
|
related_name="teachers")
|
|
|
|
# now the Teacher model is already defined we can update references
|
|
Student.update_forward_refs()
|
|
|
|
```
|
|
|
|
!!!warning
|
|
Remember that `related_name` needs to be unique across related models regardless
|
|
of how many relations are defined.
|