> > That's a bit ridiculous, because now I have to reinvent Django ORM, > contrib packages and everything under the sun.
> Django can work with DBs that support or don't support transactions. I don't know where you get the impression that Django can work with transactionless DB's from. Many of Django's features assume transactional support, e.g. the ORM features update(), delete(), get_or_create(), many-to-many fields, etc. By extension I think the contrib packages all rely on them in some way. On 10 September 2017 at 06:30, Nes Dis <[email protected]> wrote: > If I can summarize the different thoughts for having a Django connector > for nosql db like Mongodb: > > > 1. Don't mix up relational database with a document store database > - Document store DBs also have syntax for performing relation lookups > within them. Possibly complex relational operations are not supported > but > lookups from one table/collection to another is possible > 2. Use a completely new wrapper to deal with non-rel DBs > - That's a bit ridiculous, because now I have to reinvent Django > ORM, contrib packages and everything under the sun. > 3. Use 2 DBs one for contrib packages other for website specific data. > - Managing 2 DBs is a troublesome marriage. > 4. Translating SQL to Mongodb syntax is not easy/ Impossible. > - It's not easy, but has been done: djongo > <https://github.com/nesdis/djongo>. SQL DBs have a lot of features, > SQLite has very few, Django can work with DBs that support or don't > support > transactions. > > Does it matter to the end user, what the underlying DB really is? By > adding support for other DBs into Django, it's accessible to larger user > base. > > 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 [email protected]. > To post to this group, send email to [email protected]. > 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/4826023b-c697-4a0e-b43d- > 476ad9927673%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/4826023b-c697-4a0e-b43d-476ad9927673%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adam -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAMyDDM3QXvSC9TVeN19KoaOAnmwFmUGjti3KRptr9PE%3DkcRNfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
