> Do you need aggregations, database functions, joins with filtering on >> foreign keys, etc.? Then you should consider a relational database anyway. >> Or would you just like to define models and have the Django admin >> generate some nice editors for your non relational data-model? >> If the latter is the case, then that's a valid point! In fact, maybe the >> Django admin should provide hooks for extension, in order to add list- and >> detail-views, not handled by the Django-ORM-to-Django-Admin mapper. > >
> Yes, the latter case you discussed is what I wanted. All I wanted was to > have the same functionality as is there in SQL for NoSQL, and adding > support for it in the admin section too > Then maybe you should propose to add the possibility for adding List- and Detail-Views to the Django-Admin without an underlying Django-Model. You could then just use a normal Django Form and use it to edit your MongoDB model. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJ_HXxriZhLcSeYaUh5UseoT%2B%2B-gRCi5UQF7d1jzFfCaRE4U8w%40mail.gmail.com.
