On Apr 8, 10:50 am, Javier Guerra Giraldez <jav...@guerrag.com> wrote:
> A: use the _same_ ORM with NoSQL backends. then it's important to > provide (almos) every capability of the current ORM, even if they have > to be emulated when the backend doesn't provide it natively. To do this would mean to essentially implement a relational database on top of a non-relational data store. Except it would be worse, because instead of using the database's built-in logic, you'd be doing all of these operations over the network. It would also be very, very difficult to do this in a way where the abstraction wouldn't break down when doing anything non-trivial. It's just a bad idea. It's for these same reasons that some database backends throw errors for some of the aggregate operations. FWIW, I think Alex's approach has merit--only support that subset of features that the underlying database directly supports. If someone wants to build features on top of that, they can do so, but it should probably live externally to Django. At least until it becomes very stable and widely-used. Thanks, Eric Florenzano -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
