My 2 cents on this... I don't think it would be an unachievable goal to write a MongoDB backend for Django's ORM. However, it wouldn't support any relational feature, and likely would also need to skip support for some other common features, for example AutoField is actually hard to support on MongoDB. The Django ecosystem is very much written on an assumption that the underlying datastore is relational, so this would mean that even if you have MongoDB backend, you can't use it with most contrib models for example.
Even if you can't use the backend with the full ecosystem, such a backend might be very useful for some use cases. My guess is that the most common case would be usage of MongoDB as an additional data store along your relational database. I believe that most users requesting a MongoDB backend actually would want to see a backend which is a drop in replacement for the SQL backends. Unfortunately, due to the differences in optimal database schema design between relational and document oriented data stores, this is both a bad idea, and almost impossible to implement. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7f6391f8-e477-4573-b7f9-06634d1b7957%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
