On Tue, Apr 8, 2008 at 8:40 AM, Mat <[EMAIL PROTECTED]> wrote: > Why don't we start a new branch (probably off query-set) to include bigtable > support into the ORM, shouldn't all other modules work after the model > system is updated?
They should, although it shouldn't need a whole new branch, I don't think. Once qs-rf lands, it should provide enough hooks that a database backend should suffice. It still won't be simple, but it shouldn't need a branch of Django's own code. And since appengine lets you drop in your own Django codebase, we should be able to just use queryset-refactor already, even if we don't wait for it to be merged to trunk. I just don't know enough about it to venture into that myself yet. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
