On Sun, Jan 17, 2010 at 5:36 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Sun, Jan 17, 2010 at 9:37 AM, Waldemar Kornewald > <wkornew...@gmail.com> wrote: >> On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com <flo...@gmail.com> wrote: >>> I'm not really a developer on Django itself, but I am fairly >>> interested in non-relational databases, and some of the things being >>> said in this thread worry me a bit. >> >> OK, if you read my mail literally I sound like "all" nonrel DBs are >> the same. Of course they're not and you can find a counter-example for >> almost everything. There's nothing to worry about, though. The >> counter-examples simply need additional changes to get supported. It's >> not like my changes would prevent other backends. > > No, but they don't allow other backends either. From my perspective, > the purpose of this effort is to make the modifications to core that > make *any* backend that stores data possible.
It is, absolutely. I think most (if not all) of the other key-value stores need just two additions: 1. AutoField with string values 2. Extra backend-specific meta-data in Model CouchDB and other versioned backends would store the internal revision number and use that on UPDATE, for example. In my previous mail I already mentioned that probably all nonrel backends will need to know the pk column names of all tables in order to emulate JOINs and maybe a few other features. Have I missed anything? As Thomas said, I just wanted to know whether you'd suggest going on with our SQLCompiler-based solution and I'd like to know what you think about it in general. Or is it too early to say anything? Bye, Waldemar Kornewald -- http://twitter.com/wkornewald http://bitbucket.org/wkornewald/ http://allbuttonspressed.blogspot.com/
-- 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.
