Hi Malcolm, On 10 Feb., 05:25, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > I have a reasonably fleshed out plan to make things easier here in the > Django 1.2 timeframe. The rough idea is that everything under > django/db/models/sql/ could be replaced with a module of the developer's > choosing (probably set via a setting). That package is the only place > that really cares much about SQL. > > So somebody wanting a GAE backend or an Hadoop backend or something else > would write something that behaved the same way as the Query class (and > subclasses) and could be called by the QuerySet class appropriately.
Is the plan somewhere on the wiki? App Engine support requires at least that Model and probably a few other classes can be overridden (maybe partially). For example, save_base() makes a few queries to check if the row already exists, but this would have to be done differently on App Engine (hopefully with a transaction). BTW, Mitchell Garnaat, the creator of boto (popular AWS library for Python), might be interested in helping with a SimpleDB port: http://groups.google.com/group/boto-users/msg/c68e9456d2c6393e Bye, Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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 -~----------~----~----~----~------~----~------~--~---
