#8036: select_related() yields unexpected results with certain combinations of
*fields
---------------------------------------+------------------------------------
Reporter: mrmachine | Owner: mtredinnick
Status: closed | Milestone: 1.0
Component: Database wrapper | Version: SVN
Resolution: fixed | Keywords: select_related
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => fixed
Comment:
I've tried pretty hard to reproduce this, but I can't. It's quite possible
that this has been fixed with one of the changes committed since you filed
the code (you don't mention the subversion revision or release you were
testing against).
It's not possible to use your example exactly, since it refers to models
that don't exist in the sample code.
If you are still seeing the problem with current trunk, please create a
'''small''' patch against
{{{tests/regressiontests/select_related_regress/models.py}}} that fails.
The current example also suffers from having a lot of fields that are
almost certainly not relevant, so once you have a failing test case,
please remove as many fields as possible so that we can focus on the
critical pieces.
In the meantime, I'm going to mark this as fixed, because I think that's
what's happened.
--
Ticket URL: <http://code.djangoproject.com/ticket/8036#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
