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
On mongo motor when you make a query using find() method e after makes an aggregate, the aggregate will be applied above the filtered query and not above all collection.
But when using the mongomock on tests, this is not what happens, the aggregation is above all collection independent of what find() method returns. This behavior can be viewed on prints below:
Given this route, with this filter and aggregation:
When I hit it with mongo motor it returns me filtered by machine_id "6748" given on line 190
When I run the tests, it's possible see on "RESULTS" print on terminal, that all machines existents would be returned while no one should be returned
The text was updated successfully, but these errors were encountered:
On mongo motor when you make a query using find() method e after makes an aggregate, the aggregate will be applied above the filtered query and not above all collection.
But when using the mongomock on tests, this is not what happens, the aggregation is above all collection independent of what find() method returns. This behavior can be viewed on prints below:
The text was updated successfully, but these errors were encountered: