Re: Rewrite the Django wiki page

[Nes Dis]

That works :)

Thank you for the super fast reply!

On Mon, Dec 4, 2017 at 9:31 PM, Tim Graham <timogra...@gmail.com> wrote:

> You need to login using one of the buttons on the top of the page, then an
> "Edit this page" button will appear at the bottom.
>
> On Monday, December 4, 2017 at 10:36:03 AM UTC-5, Nes Dis wrote:
>>
>> I was wondering if it is possible to add some info into the Django wiki
>> page. I have been trying to find the source files(txt or rst) for the wiki
>> page of this url: https://code.djangoproject.com/wiki/NoSqlSupport
>> <https://code.djangoproject.com/wiki/NoSqlSupport>
>> I simply cannot find the github repo where this is hosted. Any help is
>> much appreciated.
>>
>> Thank you in advance!
>>
>> Nes
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/django-developers/d2CFDV4n5qc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b52ebec8-7e90-4a40-92e0-
> 1fd13c59bdca%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/b52ebec8-7e90-4a40-92e0-1fd13c59bdca%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BjAkkwCpnkufCcDx3Rowerf4EQTXXQrW_CdE_Srr1WXUkkxSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Rewrite the Django wiki page

[Nes Dis]

I was wondering if it is possible to add some info into the Django wiki 
page. I have been trying to find the source files(txt or rst) for the wiki 
page of this url: https://code.djangoproject.com/wiki/NoSqlSupport  

I simply cannot find the github repo where this is hosted. Any help is much 
appreciated. 

Thank you in advance!

Nes

-- 
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/55b93265-e3b7-446d-8d32-0a04e5b78e5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Having a MongoDB connector for Django

[Nes Dis]

I completely agree with you! Having a connector for the backend DB means 
things will be slow. This must be indicated to the end-user. The engineer 
must whether having two dbs is a better fit or a single one with some 
trade-offs.

Regards
Nes Dis

On Monday, 18 September 2017 15:22:00 UTC+5:30, Tom Evans wrote:
>
> On Fri, Sep 15, 2017 at 6:44 PM, Nes Dis <nes...@gmail.com > 
> wrote: 
> > I would like to thank everyone for their valuable comments. 
> Simultaneously I 
> > would like to comment on some conceptions regarding using MongoDB. Its 
> not 
> > accurate to state that relational joins cannot happen in MongoDB. It can 
> be 
> > done at the application level. LEFT JOIN and INNER JOIN. A detailed 
> > description of this is available. 
>
> I don't think anyone has said that this cannot be done, but instead 
> that it is not desirable to do so. 
>
> A django ORM adapter that supports Mongo would be used by people who 
> would not understand that, whilst you can do relational things using 
> mongo, it will not perform well. 
>
> In an earlier email you said: 
>
> > 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. 
>
> This is precisely the problem. If a mongodb connector was provided for 
> Django's ORM, people would expect to be able to use it with all these 
> packages that are designed to work with relational databases, and will 
> be annoyed when the project is slow once real amounts of data are 
> added. 
>
> If you want relational data, use a relational database, and use an 
> object relational mapping API to access it. If you want document data, 
> use a document store, and use an object document mapping API to access 
> it (PyMongo provides an ODM). 
>
> If you want both, choose one as your primary data store (I prefer 
> relational), all changes go through there. On modifying the primary 
> store, update the secondary store, according to your business 
> requirements (eg, instantly, batched ETL, daily, etc) 
>
> Cheers 
>
> Tom 
>

-- 
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/9c9cff0a-84c3-40f7-8d0a-61e51f68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Having a MongoDB connector for Django

[Nes Dis]

Hello

I would like to add that the application level joins are scripted such that 
they are *atomic in nature. *Which means if there is another thread/process 
operating in parallel, It will have no impact on final output. Is this why 
you feel an application join is scary?

Regards
Nes Dis

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/5252cca0-90f4-42d2-9b10-333f2a44ccd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Having a MongoDB connector for Django

[Nes Dis]

I would like to thank everyone for their valuable comments. Simultaneously 
I would like to comment on some conceptions regarding using MongoDB. Its 
not accurate to state that relational joins cannot happen in MongoDB. It 
can be done at the application level. LEFT JOIN and INNER JOIN. A detailed 
description 
<https://nesdis.github.io/djongo/integrating-django-with-mongodb/> of this 
is available.

Admin modules rely heavily on SQL, So cannot be ported to MongoDB. But 
admin porting to MongoDB is working successfully in djongo.

Regards
Nes Dis

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/e0ac0919-0ae6-4a42-ba7c-c558bc42d141%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Having a MongoDB connector for Django

[Nes Dis]

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/00ea22fe-a58f-4427-93fb-2644682b5873%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Having a MongoDB connector for Django

[Nes Dis]

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 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/4826023b-c697-4a0e-b43d-476ad9927673%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Having a MongoDB connector for Django

[Nes Dis]

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/b0ce04d1-62cb-4765-b850-06c4a5b0607f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.