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
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
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
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
