2 ms·
I assume that anyone who agrees with this post doesn't actually do programming, and would struggle to instantiate a Redis client and then use it in the simplest
by zeeg 14y ago
I assume that anyone who agrees with this post doesn't actually do programming, and would struggle to instantiate a Redis client and then use it in the simplest manner.
You cant have a RELATIONAL mapper without a RELATIONAL database, and you break nearly all of the constraints with many of these "NoSQL" solutions that the Django ORM relies on.
If you want to use NoSQL, use it. There's no reason the Django ORM needs to support it. Programming isn't hard.
- kennu 14y agoI would claim thare are benefits in a framework having a similar API for both for SQL-ORM and NoSQL-ODM. This has already been done in the Ruby on Rails world, where ActiveRecord and Mongoid exist in parallel and have similar interfaces. This makes it much easier for third party modules to support both of them. Perhaps ideally, the ORM API is a superset of the ODM API with added support for transactions and deeper relations etc. Apps that don't need those features can then easily support both.
- zeeg 14y agoWhat benefits? They're completely different technologies. They share very few characteristics, and many apps which are built on SQL using the ORM would not "just work" on a NoSQL engine. You also are only talking about MongoDB. Who cares about MongoDB? Maybe you do. What about the guy using Cassandra? Or Redis? Or Couchbase? etc etc etc They all have very different properties, and the only thing they have in common is that they store data, and some of them allow you to query on the data.