On Thu, 2008-02-21 at 01:55 -0800, cesco wrote: > Hi > > > So the SQL that is being constructed by the joined queryset isn't valid. > > I'm almost certain the answer to this is "it's fixed in > > queryset-refactor, so will one day be fixed in trunk." > > Thanks for the work you are doing:-) > > > Pull the results back into Python and merge them manually. > > Could I ask you to be a bit more specific (not so experienced with > python and django)? > You mean I should take the two query sets separately and merge them > based on the id of the objects in each of the querysets?
That's probably the right thing. It depends on what "&" is meant to be doing here. I don't know what is in those two querysets, since I've never used django-tagging, but I would guess you're trying to find instances that are in both querysets when you "&" them together. If so, then checking the id attribute will tell if you two instances are the same. Malcolm -- Why can't you be a non-conformist like everyone else? http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
