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 goal of this issue is to optimize the identified queries (see the project description) in Atlas. The optimization can happen by identifying the beanie query, removing fetch_links, and instead:
Only fetching the elements that are needed
If the element is only needed because of the id, using the trick of ref to get that id without doing an aggregation
Old description
Optimizing the queries using the approach here (https://beanie-odm.dev/tutorial/relations/#on-demand-fetch) is straightforward. The difficulty is in having a consistent approach for the methods in db_manager. Do we fetch_links per default? If not, then should we extend an interface for the methods invoking the db_manager helpers to specify whether to fetch the links, which links, and to which recursion.
We should have a consistent way of dealing with this
The goal of this issue is to optimize the identified queries (see the project description) in Atlas. The optimization can happen by identifying the beanie query, removing fetch_links, and instead:
Old description
Optimizing the queries using the approach here (https://beanie-odm.dev/tutorial/relations/#on-demand-fetch) is straightforward. The difficulty is in having a consistent approach for the methods in
db_manager
. Do we fetch_links per default? If not, then should we extend an interface for the methods invoking thedb_manager
helpers to specify whether to fetch the links, which links, and to which recursion.We should have a consistent way of dealing with this
From SyncLinear.com | AGE-203
The text was updated successfully, but these errors were encountered: