* 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>
173 lines
4.8 KiB
Markdown
173 lines
4.8 KiB
Markdown
#Pagination and rows number
|
|
|
|
Following methods allow you to paginate and limit number of rows in queries.
|
|
|
|
* `paginate(page: int) -> QuerySet`
|
|
* `limit(limit_count: int) -> QuerySet`
|
|
* `offset(offset: int) -> QuerySet`
|
|
* `get() -> Model`
|
|
* `first() -> Model`
|
|
|
|
|
|
* `QuerysetProxy`
|
|
* `QuerysetProxy.paginate(page: int)` method
|
|
* `QuerysetProxy.limit(limit_count: int)` method
|
|
* `QuerysetProxy.offset(offset: int)` method
|
|
|
|
## paginate
|
|
|
|
`paginate(page: int, page_size: int = 20) -> QuerySet`
|
|
|
|
Combines the `offset` and `limit` methods based on page number and size
|
|
|
|
```python
|
|
class Track(ormar.Model):
|
|
ormar_config = ormar.OrmarConfig(
|
|
database=databases.Database(DATABASE_URL),
|
|
metadata=sqlalchemy.MetaData(),
|
|
tablename="track"
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
album: Optional[Album] = ormar.ForeignKey(Album)
|
|
name: str = ormar.String(max_length=100)
|
|
position: int = ormar.Integer()
|
|
```
|
|
|
|
```python
|
|
tracks = await Track.objects.paginate(3).all()
|
|
# will return 20 tracks starting at row 41
|
|
# (with default page size of 20)
|
|
```
|
|
|
|
Note that `paginate(2)` is equivalent to `offset(20).limit(20)`
|
|
|
|
## limit
|
|
|
|
`limit(limit_count: int, limit_raw_sql: bool = None) -> QuerySet`
|
|
|
|
You can limit the results to desired number of parent models.
|
|
|
|
To limit the actual number of database query rows instead of number of main models
|
|
use the `limit_raw_sql` parameter flag, and set it to `True`.
|
|
|
|
```python
|
|
class Track(ormar.Model):
|
|
ormar.OrmarConfig(
|
|
database=databases.Database(DATABASE_URL),
|
|
metadata=sqlalchemy.MetaData(),
|
|
tablename="track"
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
album: Optional[Album] = ormar.ForeignKey(Album)
|
|
name: str = ormar.String(max_length=100)
|
|
position: int = ormar.Integer()
|
|
```
|
|
|
|
```python
|
|
tracks = await Track.objects.limit(1).all()
|
|
# will return just one Track
|
|
```
|
|
|
|
!!!note
|
|
All methods that do not return the rows explicitly returns a QuerySet instance so you can chain them together
|
|
|
|
So operations like `filter()`, `select_related()`, `limit()` and `offset()` etc. can be chained.
|
|
|
|
Something like `Track.object.select_related("album").filter(album__name="Malibu").offset(1).limit(1).all()`
|
|
|
|
## offset
|
|
|
|
`offset(offset: int, limit_raw_sql: bool = None) -> QuerySet`
|
|
|
|
You can also offset the results by desired number of main models.
|
|
|
|
To offset the actual number of database query rows instead of number of main models
|
|
use the `limit_raw_sql` parameter flag, and set it to `True`.
|
|
|
|
```python
|
|
class Track(ormar.Model):
|
|
ormar.OrmarConfig(
|
|
database=databases.Database(DATABASE_URL),
|
|
metadata=sqlalchemy.MetaData(),
|
|
tablename="track"
|
|
)
|
|
|
|
id: int = ormar.Integer(primary_key=True)
|
|
album: Optional[Album] = ormar.ForeignKey(Album)
|
|
name: str = ormar.String(max_length=100)
|
|
position: int = ormar.Integer()
|
|
```
|
|
|
|
```python
|
|
tracks = await Track.objects.offset(1).limit(1).all()
|
|
# will return just one Track, but this time the second one
|
|
```
|
|
|
|
!!!note
|
|
All methods that do not return the rows explicitly returns a QuerySet instance so you can chain them together
|
|
|
|
So operations like `filter()`, `select_related()`, `limit()` and `offset()` etc. can be chained.
|
|
|
|
Something like `Track.object.select_related("album").filter(album__name="Malibu").offset(1).limit(1).all()`
|
|
|
|
|
|
|
|
## get
|
|
|
|
`get(**kwargs) -> Model`
|
|
|
|
Gets the first row from the db meeting the criteria set by kwargs.
|
|
|
|
If no criteria is set it will return the last row in db sorted by pk.
|
|
(The criteria cannot be set also with filter/exclude).
|
|
|
|
!!!tip
|
|
To read more about `get` visit [read/get](./read/#get)
|
|
|
|
|
|
## first
|
|
|
|
`first() -> Model`
|
|
|
|
Gets the first row from the db ordered by primary key column ascending.
|
|
|
|
!!!tip
|
|
To read more about `first` visit [read/first](./read/#first)
|
|
|
|
|
|
## QuerysetProxy methods
|
|
|
|
When access directly the related `ManyToMany` field as well as `ReverseForeignKey`
|
|
returns the list of related models.
|
|
|
|
But at the same time it exposes subset of QuerySet API, so you can filter, create,
|
|
select related etc related models directly from parent model.
|
|
|
|
### paginate
|
|
|
|
Works exactly the same as [paginate](./#paginate) function above but allows you to paginate related
|
|
objects from other side of the relation.
|
|
|
|
!!!tip
|
|
To read more about `QuerysetProxy` visit [querysetproxy][querysetproxy] section
|
|
|
|
### limit
|
|
|
|
Works exactly the same as [limit](./#limit) function above but allows you to paginate related
|
|
objects from other side of the relation.
|
|
|
|
!!!tip
|
|
To read more about `QuerysetProxy` visit [querysetproxy][querysetproxy] section
|
|
|
|
### offset
|
|
|
|
Works exactly the same as [offset](./#offset) function above but allows you to paginate related
|
|
objects from other side of the relation.
|
|
|
|
!!!tip
|
|
To read more about `QuerysetProxy` visit [querysetproxy][querysetproxy] section
|
|
|
|
[querysetproxy]: ../relations/queryset-proxy.md
|