I'm in agreement with most of the others - that Django should not strive to achieve compatibility with a bunch of different database types simply to open itself up to a larger user base. The cost you pay is a lack of functionality that takes advantage of the specific features granted by a particular technology choice.
Joins and their different types (LEFT/FULL) are an integral part of the assumptions made about the ORM, as are aggregations, grouping, relationships, indexes, migrations. As you can see with most attempts to shoehorn non-relationship databases into django ORM backends, you lose a lot of functionality. If Django were to adopt these backends as official, then we're stuck in one of two positions. The first is that we hamstring all databases to achieve the lowest common feature set. The second is that we have a bunch of feature flags and documentation that work around the incompatibilities between technologies. Neither of these options are attractive. If you want to use a non-relational database, that's fine. Django doesn't specifically cater to those technology choices or users, and that's ok. There are other frameworks one may use. On Monday, 11 September 2017 13:28:55 UTC+10, Nes Dis wrote: > > Thank you all for your very insightful comments. I personally am a big > user/contributor to the framework myself and would like to see it thrive > and progress with respect to other competing frameworks. > > I am sure most are aware, of this argument about MongoDB increasing in > popularity. Several members are of the opinion that not supporting this > backend (which in my opinion is not too difficult) will not dent Django's > popularity. > > In conclusion, I do hope this is the right decision for Django will take > it in the correct direction! > > Regards > Nesdis > > > > On Friday, 8 September 2017 18:33:59 UTC+5:30, Nes Dis wrote: >> >> Hello >> >> I am wondering what is the state of the art on Django having a backend >> connector for MongoDB database backend. There are a few solutions out there >> but they don't work as expected. >> >> A possible solution for this is to have a connector which translates SQL >> queries created in Django, into MongoDB queries. >> >> I would like to hear the *expert opinion *from the esteemed members of >> this group on this concept. >> >> A working solution for this can be found here: djongo >> <https://nesdis.github.io/djongo/>. (Django + Mongo = Djongo) The >> project is hosted on github. >> >> Regards >> Nes Dis >> > -- 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/ac3907d3-dc99-4427-976d-fa992d589343%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
