Hi Alex, On Jun 7, 9:35 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > As you can see the fruits of these efforts have already begun to land > in my branch, and I suspect that the multidb refactorings of last year > have left us in a better state than I appreciated: while the concepts > and data structures used in the Query class are relational/SQL biased > (joins, where vs. having, etc.), the data itself is entirely backend > neutral. This means that getting a "stupid" MongoDB backend that can > handle trivial filters should be relatively easy, and then it can be > evolved to work with the better datastructures I'll be refactoring > Queyr to eventually use.
Did you already take a look at our MongoDB backend for Django-nonrel: http://github.com/aparo/django-mongodb-engine This could save you some time. Also, maybe you'll find it helpful to see what we had to change in Django to get that backend to work: https://docs.google.com/leaf?id=0B3LqunL-SCJJNTNiNWE3ZmUtYWIxZi00ZWExLTk4YTktYjM4MzNiZTA0MGNh&hl=en I guess by now you're not suprised by the size of the patch, anymore. ;) You'll certainly find a few similarities to your branch (like the AutoField change or has_results()). Couldn't some parts of has_results() be reused by NoSQL backends? For example, clear_ordering() and set_limits() are completely independent of the backend itself. Why did you revert the AutoField patch? BTW, in the Django-nonrel patch you'll find a few other changes which were related to AutoField: ForeignKey needs to find out the actual database type instead of having a hard-coded IntegerField. We added related_db_type() for this purpose. Maybe you can reuse or adapt some of our code. Still, Django has a few unit tests which assume that assigning a string to an AutoField will fail, so we'll need to find a solution for that (probably by fixing the unit tests). Bye, Waldemar Kornewald -- 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.
