On Sep 13, 2008, at 7:11 PM, Russell Keith-Magee wrote:
> > On Sun, Sep 14, 2008 at 7:24 AM, Martin Diers <[EMAIL PROTECTED]> wrote: >> >> On Sep 6, 2008, at 11:36 AM, Posi wrote: >>> >>> Still though, how tied are we to a true relational model and how >>> does >>> that tie to a column based DB. >> >> So utterly and completely, that if you wished to use HBase, there >> would be no possible way to integrate in into the current ORM. > > This answer is utterly and completely untrue. > > One of the outcomes of the recent queryset-refactor was to decouple > the SQL specific parts of the ORM from the queryset itself. Writing a > non-SQL backend for queries is now in the realm of possibility (and > during DjangoCon, I heard at least one mention of a prototype CouchDB > backend). Obviously, there will always be limitations - the concept of > 'joins' on CouchDB is a little vague, for example - but basic data > queries can definitely be integrated. > > To be clear - this doesn't mean "writing a CouchDB backed is a 30 > minute job for a newcomer", and there aren't any tutorials on how to > do this, and if you try and it breaks you get to keep every single one > of the shiny pieces. However, it is _possible_, and I for one am > interested in seeing support for non-SQL databases in the Django > world. > > Yours > Russ Magee %-) > Point taken, and I should have read the post better. Although the current ORM would need to be extended to gain the true power of a column oriented DB. When I think of where things like a ColumnSet fits into the Django ORM, I start to get dizzy. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
