#6658: Unexpected select_related() behaviour
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Component: Database
wrapper
Version: SVN | Resolution:
Keywords: select_related, exclude qs-rf | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------------+------------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
Please post the relevant fields from you model. If {{{Thread.forum}}} is a
!ManyToMany relation, you have multiple colliding bugs here.
{{{exclude()}}} with many-to-many is a bit flawed at the moment.
Could you also check that for the three elements returned in the first
query, there really are existing entries in those related tables. I can't
see why there wouldn't be, but let's rule that out. I can't quite repeat
your problem at the moment, but that's partly because I'm fixing exclude()
first, which could well change the results of your first query (although,
again, I don't quite see how at the moment). Understanding which breakage
you're hitting will help.
--
Ticket URL: <http://code.djangoproject.com/ticket/6658#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
