On Apr 8, 12:32 pm, Waldemar Kornewald <wkornew...@gmail.com> wrote:
> What I'm proposing is not a complete emulation of all features at all > cost, but simply an automation of the things that are possible and in > wide use on nonrel DBs. Moreover, you'd only use these features where > actually needed, so this would be a helper that replaces exactly the > code you'd otherwise write by hand - nothing more. Denormalization, > counters, etc. indeed go over the network, but people still do it > because there is no alternative (CouchDB being an exception, but there > we can auto-generate a view, so the index is created on the DB: same > game, different location). "Denormalization, counters, etc." is a completely orthogonal problem. Solving those problems would help even those who are using relational databases, in fact. But just because it's useful, and precisely because it's orthogonal, means it doesn't belong in this summer of code project. I think what you're going to run into is that since CouchDB, Cassandra, MongoDB, GAE, Redis, Riak, Voldemort, etc. are all so vastly different, that attempting to do *any* emulation will result in serious pain down the line. It simply doesn't seem reasonable to claim that whatever refactoring Alex does, will make "it more difficult or even impossible to implement an emulation layer" because all he would be doing is decoupling SQL from the query class. That can *only* make your goal easier. Thanks, Eric Florenzano -- 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.
