Hey all, This past week was mostly spent getting lookup's working (and negation), that's gone fairly well. Well enough, in fact, that I spent most of today getting some low hanging fruit working: namely ordering, slicing, and values. In slicing we've come to an interesting design decision. Attempting to do a LIMIT 0's equivilant in MongoDB results in the full result set being returned, not a 0 item result set, as SQL does. So the question is: do we emulate the SQL (and CPython) behavior here, or do we simply write it off as a platform specific issue. In this case the emulation happens to be painless, efficient, and simple to implement, however in many other cases it will not be.
My goal for this week is going to be playing with cleaning up the abstractions in aggregates and F expressions (MongoDB has limited support for inplace updates, so this will be a useful test). Thoughts welcome, Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me -- 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.
