Ditto I haven't got a clue about how qs-rf works behind the scenes, only catch I can see is bigtable doesn't support joins (as I understand it), so that could be a limitation, but I guess multiple db requests isn't beyond reason.
You can certainly run your own django version on appengine, but without db support its limited, even sqlite wont work, as we don't have filewrite access :(, needs a new db backend adding into django as far as I can tell. Mat -----Original Message----- From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Marty Alchin Sent: 08 April 2008 14:01 To: django-users@googlegroups.com Subject: Re: Google App Engine & Django 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 -~----------~----~----~----~------~----~------~--~---
