Wow, this fits perfectly into a project I am currently working on. I love how I think of problems and miraculously the solution appear on Hacker News. Not the first time this has happened.
Yep. It almost seems like magic sometimes. I'm really happy to see what looks like a solid mongodb solution for django. Everything else I've seen didn't quite strike me. Interested in trying this one out.
i've contributed bits & pieces to mongoengine, and plan on using it in production next month. its a very well-designed, well-implemented, and actively growing ORM for mongodb, and definitely worth checking out.
and when i say "actively growing", i don't mean it in a derogatory way.
if you're using python and mongo, mongoengine is worth your attention.
we use it @ pitchfork for internal analytics and a few other projects that'll be live soon. im also using it (and mongo) to query retrosheet's game log data quickly and, well, sanely.
I'm trying to understand why there would be any ORM connotation since one of the big points of NoSQL is that there are no object to relation mappings as such in the first place.
Perhaps I am missing something.
[edited] Nothing against the project. I actually think its great.
MongoEngine just brings some structure back to MongoDB to make it easier to work with and reduce bugs in your code.
This doesn't mean to say that it imposes strict mappings, you are still free to store and retrieve what you want, even change the data model at any time.
MongoEngine includes MongoDB backends for Django auth and sessions frameworks. Also the API overlap with Django's ORM means that in some simple cases, MongoEngine Documents may be used in place of Django's models (e.g. this appears to work with Django's pagination). Not complete support, but a step or two closer!
