Hi all, On Thu, Apr 8, 2010 at 12:55 AM, Waldemar Kornewald <wkornew...@gmail.com> wrote: > On Wed, Apr 7, 2010 at 5:22 PM, Alex Gaynor <alex.gay...@gmail.com> wrote: >>> Other issues that spring to mind: [...] > Well, you might be able to quickly adapt the MongoDB backend to GAE > (within GSoC time constraints) due to their similarity. Anyway, there > is common ground between the NoSQL DBs, but this highly depends on > what problem we agree to solve. If we only provide exactly the > features that each DB supports natively, they'll appear dissimilar > because they take very different approaches to indexing and if this > isn't abstracted and automated NoSQL support doesn't really make sense > with Django. OTOH, if the goal is to make an abstraction around their > indexes they can all look very similar from the perspective of > Django's ORM (of course they have different "features" like sharding > or eventual consistency or being in-memory DBs or supporting fast > writes or reads or having transactions or ..., but in the end only few > of these features have any influence on Django's ORM, at all). > > Bye, > Waldemar Kornewald
Could we switch to one issue/feature per thread, please? I think the overall approach is chosen already, and everyone agreed with it. And each detail now has to be discussed separately, and overall discussion continued here. I.e, I have few words about design of counters and indexes (and my favorite NoSQL Berkeley DB), but not arrays/lists. -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: bu...@live.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.
