Hi Chris, On 17 déc. 2013, at 17:50, Chris Wilson <ch...@aptivate.org> wrote:
> There is no particular reason NOT to do it, unless one wants Django's ORM > layer to remain fundamentally tied to SQL. I don’t understand your sentence. To me it’s as if you were saying “there is no particular reason NOT to relay email with Django, unless one wants Django to remain fundamentally tied to HTTP”. Django’s ORM is entirely designed to translate between an object oriented API and SQL. That’s what its name says. It achieves this through roughly five layers that bride the abstraction gap. Django’s ORM is fundamentally tied to SQL. It isn’t a choice, a policy or a wish. It’s a fact. Its APIs were designed according to the capabilities of SQL databases. I don’t believe they’re well suited to NoSQL storage engines. There’s also more diversity in the NoSQL field, making it less valuable to write a common API. The least common denominator may turn out to be very small. Of course, you could implement a totally new piece of software that interfaces with both SQL and NoSQL storage engines. You’ll most likely end up with a very different design from Django’s ORM and hopefully a different API too. > I can't see a good reason to do that, but maybe others do. In the mean time, > this question will continue to be asked until a position is officially > documented, The core team doesn’t issue press releases with official positions :) However, as far as I know, most core devs would subscribe to Tom’s answer. > even if it's "we don't care about NoSQL, just leave us alone.” You’re framing the debate unfairly. There’s a difference between “we don’t think this is the right solution” and “we don’t care about your problem”. If I didn’t care, I would simply have ignored your email. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/42E0BE24-97D7-4549-AF6C-A778BFAE5545%40polytechnique.org. For more options, visit https://groups.google.com/groups/opt_out.