Decouple the Query Builder and the Engine/Executor

[unownone]

Well, I know we already have bunnet which is basically the synchronous flavour of Beanie. But what if we could decouple the query builder only.

What I am looking for :

• I will gnerate a query ( aggregate/delete/ find ,etc ) and the query builder basically generates the query at the end to be sent over to MongoDB using Motor . If instead I had a helper function which would just generate the created_query for me , which I can then run using Pymongo/motor , or anything else.

This way it'll be easier to have custom things implemented. Something that Beanie hasn't implemented yet can be implemented.

One thing would be running an explain query Or printing out the final query for debugging purposes.

what do you think about this? @roman-right