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
The next thing we want is the implementation of .find_many()
.find_many() would work just like .find() except it instead of returning Option<Entity> it would return Option<Vec<Entity>>
We would have to establish some constraints/parameters around the size of the result set of .find_many()
Since we allocate space in the runtime for the result of .find() (and .get()) we would need to set some max size that can be allocated for .find_many() results
Maybe this is configurable?
The text was updated successfully, but these errors were encountered:
.find()
onEntity
#1437 we now have.find()
usage.find_many()
.find_many()
would work just like.find()
except it instead of returningOption<Entity>
it would returnOption<Vec<Entity>>
.find_many()
.find()
(and.get()
) we would need to set some max size that can be allocated for.find_many()
resultsThe text was updated successfully, but these errors were encountered: