fix: typo QueySet -> QuerySet (#656)

Co-authored-by: Benjamin Mollier <benjamin.mollier@meetap.de>
This commit is contained in:
Boemjay
2022-05-07 13:15:26 +02:00
committed by GitHub
parent ade794aa61
commit 3917cce642
5 changed files with 9 additions and 9 deletions

View File

@ -168,7 +168,7 @@ Product.objects.filter(
```
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.
@ -795,7 +795,7 @@ assert owner.toys[1].name == "Toy 1"
```
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.

View File

@ -148,7 +148,7 @@ fields and the final `Models` are fetched for you.
them in select_related.
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.
@ -366,7 +366,7 @@ fields and the final `Models` are fetched for you.
them in select_related.
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.

View File

@ -69,7 +69,7 @@ tracks = await Track.objects.limit(1).all()
```
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so you can chain them together
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.
@ -103,7 +103,7 @@ tracks = await Track.objects.offset(1).limit(1).all()
```
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so you can chain them together
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.

View File

@ -174,7 +174,7 @@ await Car.objects.select_related('manufacturer').fields({'id': ...,
```
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.
@ -285,7 +285,7 @@ await Car.objects.select_related('manufacturer').exclude_fields([{'company': {'n
excluded.
!!!note
All methods that do not return the rows explicitly returns a QueySet instance so
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.

View File

@ -141,7 +141,7 @@ album.signals.pre_save.disconnect(before_save)
* bulk operations (`QuerySet.bulk_create` and `QuerySet.bulk_update`) as they are designed for speed.
* queyset table level operations (`QuerySet.update` and `QuerySet.delete`) as they run on the underlying tables
* queryset table level operations (`QuerySet.update` and `QuerySet.delete`) as they run on the underlying tables
(more lak raw sql update/delete operations) and do not have specific instance.
### pre_save