You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/content/advanced/dataloaders.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Avoiding the N+1 Problem With Dataloaders
2
2
3
3
A common issue with graphql servers is how the resolvers query their datasource.
4
-
his issue results in a large number of unneccessary database queries or http requests.
4
+
This issue results in a large number of unneccessary database queries or http requests.
5
5
Say you were wanting to list a bunch of cults people were in
6
6
7
7
```graphql
@@ -129,7 +129,7 @@ impl Cult {
129
129
130
130
Once created, a dataloader has the functions `.load()` and `.load_many()`.
131
131
When called these return a Future.
132
-
In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_may(Vec<i32>)` it would have returned `Future<Vec<Cult>>`.
132
+
In the above example `cult_loader.load(id: i32)` returns `Future<Cult>`. If we had used `cult_loader.load_many(Vec<i32>)` it would have returned `Future<Vec<Cult>>`.
0 commit comments