On Wed, Aug 25, 2010 at 5:08 PM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Wed, Aug 25, 2010 at 10:21 PM, Waldemar Kornewald > <wkornew...@gmail.com> wrote: >> On Wed, Aug 25, 2010 at 2:36 PM, Russell Keith-Magee >> <russ...@keith-magee.com> wrote: >>> On Wed, Aug 25, 2010 at 4:00 PM, Waldemar Kornewald >>> <wkornew...@gmail.com> wrote: >>>> As Alex' MongoDB backend demonstrates, all nonrel backends can >>>> retrieve the Query's filters. >>> >>> No - Alex's MongoDB backend demonstrates that the basic query >>> requirements of MongoDB can be met. >> >> MongoDB is basically a superset of the other DBs. That's why we chose >> it for GSoC. Cassandra can only do pk queries. So can MongoDB. App >> Engine has filtering support. So has MongoDB. CouchDB supports >> embedded documents. So does MongoDB. >> >> Of course some DBs have extra features like map/reduce or optimistic >> locking, but those can't be mapped to Django's current ORM, anyway, so >> they need platform-specific APIs. >> >> What you're expecting here (4 backends!) is a *lot*. Who will write >> those backends? If that's what you want then the merge might have to >> wait for Django 1.5 or later. > > I'm not saying that 4 *finished* backends is a pre-requisite for > merging to trunk. > > What I'm saying is that 4 *proof of concept* backends would be enough > to satisfy me that enough people have looked at the API we're > proposing in sufficient detail to validate that it's sufficient for > the task. > > The backends themselves aren't the important feature in all this. The > important features are: > * the eyeballs that come along for the ride -- preferably, several > pairs of them, with in-depth knowledge and experience in the various > platforms we're looking to service with these changes; and > * the hard evidence that they've actually looked into the problem, > not just glanced at the API and assumed that everything will work the > way it needs to.
That might take a while. Writing a backend isn't trivial and few people can afford to first write a backend and then implement their project on top of it. I've know of two people interested in writing a CouchDB and Cassandra backend, but as always "being interested" doesn't mean that they'll find the time to do it. I'd still rather get something out to attract the first users, then get the first complaints about missing features, and suddenly those who complain have incentive to help fix the issue. That's easier than waiting for someone to deal with unofficial technology. At least then officially ask for help on the Django blog and the Django discussion groups. Just leaving Alex' work in some separate branch probably won't lead to the desired results. Bye, Waldemar Kornewald -- Django on App Engine, MongoDB, ...? Browser-side Python? It's open-source: http://www.allbuttonspressed.com/blog/django -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
