4 ms·

This could help out those who are building projects using Django &/or Django-nonrel.

• zoomzoom 16y ago
  Kind of kills one of the main reasons for the nonrel branch to exist, no? Wasn't django-nonrel an outgrowth of efforts to put django on appengine? I think that the nonrel project has utility on other places (redis, mongo, etc...) but ABP (all buttons pressed, creators of nonrel) was pushing django on GAE alot, IIRC.
  • jjm 16y ago
    I agree. Don't forget that work has begun for a Cassandra driver as well. Truth be told however, Django and a SQL based system aren't all that bad. No matter what, it will be a long time before Django gets full 1.0 support for NoSql in any shape or form. That means, 100% Django coverage.
  • wkornewald 16y ago
    It depends on who you ask. :) We've created Django-nonrel and djangoappengine for people who need GAE's scalability or at least don't want to deal with scalability as an afterthought. Of course using the GAE datastore for everything can be really painful (and dbindexer is supposed to help in this regard - at least a little bit), but now you can have the best of both worlds and pick the right tool for the task.
• charlemagne 16y ago
  I'm looking forward to testing out porting one of my Django apps to GAE, particularly since the Heroku clones for Django are not yet ready for public consumption.