So anyways... Google App Engine is a special case. It is not nearly as robust a database solution as something like CouchDB or MongoDB - but then again it was never meant to be. The direction from the beginning was on scaling, even if it meant dropping features. The BigTable ORM lacks many of the functions necessary for implementing the Django ORM on that database. Python-only solutions to these gaps would not scale as well as low-level database APIs, and as such would probably not scale well enough to be useful. The situation has not improved because Google doesn't see a need. App Engine fits in an even more specialized niche than most NoSQL solutions.
That said, a lot of work has been done to make Django useful on that platform. My own web site runs Django 1.2.1 on App Engine. Things like auth, caching, and sessions have been implemented without porting the ORM. So really, the only barrier to "pure" Django on App Engine is the model, which needs to be rewritten for each application used on GAE. Now django-nonrel is doing some excellent work to try to implement a workable ORM on App Engine. However, I'm sure they are facing an uphill battle because of the constraints of the platform. I have no doubt that they will indeed produce a workable solution in time, though. I've been doing lots of research with Django on GAE, and am actually using it in production. If you're interesting in this particular stack, please contact me off-list and I can attempt to answer any questions that you have. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
