On Jul 15, 8:54 am, Up2L8 <[email protected]> wrote: > Is there any way Ticket #10977 could get rolled up into the 1.1 > release? > > Using the intersection and union operators seems borked for some > applications and it sounds like this should fix it.
I guess I should mention that it seems that a workaround exists using set(QS1) & set(QS2). This evaluates properly (where QS1 & QS2 does not). Probably not the best implementation since it doesn't condense into a single query but sufficient for my purposes. Thanks, Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
