On Sunday, June 24, 2012 10:31:41 PM UTC+8, Cezar Jenkins wrote: > > I'm only lightly involved in the project, but there is some misinformation > going around about it. > > On Sun, Jun 24, 2012 at 5:47 AM, Daniel Greenfeld <pyda...@gmail.com> > wrote: > >> >> >> We evaluated django-nonrel for use in projects and looked again at >> django-nonrel for our talk at DjangoCon Europe. To summarize our >> findings and opinions: >> >> 1. django-nonrel is stuck on Django 1.3, which has some security >> implications. > > 1.4 support is implemented and being tested in a beta mode right now. >
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. > 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/ > > 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. 1. http://django-nonrel.readthedocs.org lacks any sort of team/contributor listings. 2. https://github.com/django-nonrel/mongodb-engine/blob/master/AUTHORS.rst has 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? > > 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. :-) 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.
