MongoDB contribution? about odata-query

[OliverHofkens]

I personally have zero experience with MongoDB, but I'll happily review (and learn in the process) any contributions!
Thanks for your interest!

[cblegare]

At first sight, I feel the main issue would be that for SQLAlchemy and DjangoORM it seems you inspect the ORM declarations to help infer the type conversion to use. That means that a ODM mapping would be useful to do the same job, but there are many and much less useful and used than ORMs mentioned above. I'll look into this a bit deeper and stay in touch

[OliverHofkens]

(Again, I have no MongoDB experience so excuse me if what I say is nonsense)
If there is no "mainstream" ORM/ODM for MongoDB, then perhaps the transformer could just output a "naive" query, unaware of the structure or types of the underlying data.

An earlier version of this library did the same for Django, the only downside was that an error would only be noticed when the query actually fires and the database complains (maybe a column didn't exist or a wrong type was used). So it was pretty hard to show the user a clear error, without mapping every possible database error to a user-friendly error.
The model and type introspection were added later in order to pull some benefits of having the ORM into this library, by catching errors earlier and return meaningful messages to the end user.

If I find some extra time I'll read up a bit on MongoDB, so maybe I can offer some more useful feedback 😄