This is a good idea. One of the problems I see with this is the fact that for some ecto queries we already generate aggregate pipelines (with max, min, count, etc).

What parts we normally extract from the Ecto.Query should we generate in this case? Only the MongoDB's query object or also the projection?

It shouldn't be that hard to do, the main part of the query is translated by NormalizedQuery.query/3, you can probably use that.

I have to admit, I'm a little bit ashamed of the code in normalized_query.ex, maybe this will nudge me to refactor it a little 😃

Add function for generating mongodb query from ecto query #46

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions