Bigtable doesn't support joins so its probably going to be quite hard to integrate django ORM with it. Could be a fun little project though. You would have to manually do the joins by doing multiple bigtable requests. If I have some free time over the summer I tempted to have a bash at it but it will require a lot of work and wont be very efficient. It might be an idea to just add basic support without joins so that things like the admin interface and auth work and then build up from there.
Sam On Apr 8, 1:40 pm, "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? > > Mat > > -----Original Message----- > From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] > > On Behalf Of Marty Alchin > Sent: 08 April 2008 13:33 > To: django-users@googlegroups.com > Subject: Re: Google App Engine & Django > > On Tue, Apr 8, 2008 at 8:16 AM, Marc Garcia <[EMAIL PROTECTED]> wrote: > > Well, it seems that you just need to migrate your django models to > > appengine models. > > The trouble is who "you" are. I make use of a number of third-party > apps, and I don't much enjoy the idea of having to migrate *their* > models over to appengine, only to have to keep those changes in sync > with other updates to the apps. > > Maybe after queryset-refactor lands, we can get a BigTable backend to > actually run all existing apps, including the built-in auth and admin > apps. A pipe dream, I expect, but that's my hope, anyway. > > -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 -~----------~----~----~----~------~----~------~--~---
