Note that I've talked about the issues that nonrel has, and there are many. That said, I have some responses below. I'm not trying to be the nonrel spokesperson.
On Tue, Jun 26, 2012 at 3:34 PM, Daniel Greenfeld <pyda...@gmail.com> wrote: > > I don't mean to pick bones, but looking at the github account, BETA > apparently means being a port with stern warnings about not using it right > now. > It's not tested enough for production yet, no. Though there are those testing it right now, at least on AppEngine. On the thread I link later on you can see the discussion. > > >> 2. django-nonrel is unsupported. It switched maintainers and the >>> current maintainer is not working on it. >> >> Django-nonrel is very much maintained. Look at the github >> https://github.com/**django-nonrel/ <https://github.com/django-nonrel/> >> >> > This does not match what someone claiming to be the current lead > maintainer said to me personally after my talk in front of dozens at > DjangoCon Europe. > > While I understand this sort of misinformation I may have spread is > annoying to you, imagine how it comes to the rest of us when project > leadership is not clear. > Jonas is hesitant to lead the project, and I understand where he's coming from. For a long time there were only Mongo people maintaining the project. In a project where 80% of the users are using it for AppEngine, that can be a problem for hammering out bugs. If you look at the thread at https://groups.google.com/forum/?fromgroups#!searchin/django-non-relational/1.4/django-non-relational/_OFjwuPjc88/iqLqnEGauNwJyou'll see there are people doing active development on non-relational. Last I heard Jonas wanted to do a new release of mongodb-engine. He might have meant to say he was not maintaining the project anymore, but he's not the only one with commit access. > > 1. http://django-nonrel.readthedocs.org lacks any sort of > team/contributor listings. > 2. https://github.com/django-nonrel/mongodb-engine/blob/master/AUTHORS.rsthas > people in it who may no longer maintain it. > > What's going on? What can django-nonrel do to make it much more clear to > everyone who is involved and who is the actual leadership? > There's a big documentation issue. It's known. Migration for All Button Pressed to the new "rag tag" team is slow, but I'm sure it'll get there. > >> I have to agree with you here. The nature of the Django ORM makes >> anything like this a hack. Not much choice in that regard. >> >> I've wondered if it's possible to make an ORM that API compatible with >> forms/admin/etc that doesn't hack onto the existing ORM? >> >>> >>> In my humble opinion, the answer is no. ORM is for mapping objects onto > relational databases, and the entire API is designed around that concept. > MongoDB is a Document store and should be handled differently. > Django-nonrel adds a lot of magic, not necessarily in code, but in API > design. It turns non-relational databases into relational databases, IMO > removing many of the advantages of those systems for little gain except for > in early speed of development. > > The trick is, as I believe others have raised, is how to get Admin and > Forms and other things in Django to work with MongoDB. :-) > I have to agree, that's the big one. Though I the ecosystem of 3rd party apps is what makes using Django so great. If there is one ORM for 99% of the apps out there, and only one that works Mongo, then the only real use case of Django is going to be a system where you're using a RDBM in combination with Mongo. > > Danny Greenfeld > >> -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/VktFJetdkWIJ. > > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
