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, T
On Fri, Sep 15, 2017 at 6:44 PM, Nes Dis 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 ap
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 Fr
You're right for pointing out that some elements of a relational database
can be emulated in a non relational one, like Mongodb. The in-python joins
sound s bit scary though.
However I would argue that if you find yourself needing such things your
data is relational, and therefore a relational dat
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
I agree with everyone, no relation with relational should not be mixed
because they solve different problems.
On the other hand, having an Object Document Manager (instead of an ORM) if
required could be a possibility, right?
I think until a lot of people have that need, it won't happen.
I've u
W dniu poniedziałek, 11 września 2017 05:28:55 UTC+2 użytkownik Nes Dis
napisał:
>
> 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
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
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
parti
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 mem
I would like to add to this discussion just the clarification that, when we say
Django relies on transactions, we don't mean that it is impossible to write a
database backend which doesn't implement them -- but that Django assumes
transactional behavior to protect data integrity. It can work wit
Hello,
This discussions seems to have started with a misunderstanding of what Django
is.
Here's a very incomplete list (in advance, apologies to everyone for everything
that I'm inevitably going to omit)
1. The Django community
1.a. Django Girls
1.b. Conferences, events
>
> 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
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 oper
Another voice piling on to the "this is not a good idea" train. I inherited
a Mongo backed project at my day job that is filled with data that should
have been put in a relational database. Mongo is the wrong tool for the job
(and we're migrating off it). I tried putting an ORM in front of it to ma
JSON support in postgres is a great middle ground for storing unstructured
documents.
I don't know the specifics of your application, but I would be surprised if
a document orientated database is a perfect fit. The majority of such apps
are semi-structured, where you have some relations but also s
I agree, I think forcing Django's ORM to work on MongoDB is not a great
idea. Django relies heavily on transactions and other relational goodness.
Have you tried storing JSON in your Postgres/MySQL database? Django can
work with that with contrib.postgres/django-mysql 😉
On 8 September 2017 at 16:
Short answer: always use the appropriate tool
Relational databases and document stores have different uses and
purposes. Using a document store like a relational database (eg, with
an ORM (emphasis on the R)) is a bad idea, and using a relational
database as a document store is similarly foolish.
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 Mo
19 matches
Mail list logo