On 2/27/07, Mike Axiak <[EMAIL PROTECTED]> wrote: > > Anyway, I'm about to overload the Q object. In this new object, Q' (i > still haven't got a good name for it), will look up the tree (or down) > for any ORs, and switch the join type from 'INNER JOIN' to 'OUTER > JOIN'. > I may have to overload QAnd and QOr as well. > > I was wondering, is there anything in the works like this? Are there > better ways of doing this?
There are some plans to rework the internals of QuerySets to make the construction of custom queries a little easier, and to allow queries to span a little more of the potential range of SQL. There was a message on the django-developers list (from Malcolm Tredinnick) discussing this exact issue. If you have a use case that you think should be considered in this redesign, join in on that conversation. In the interim, the approach you have described sounds reasonable. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
