#9554: select related - maximum depth
-----------------------------------+----------------------------------------
Reporter: gert | Owner: nobody
Status: reopened | Milestone:
Component: Contrib apps | Version: 1.0
Resolution: | Keywords: select related
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by mtredinnick):
This doesn't sound like a clear problem description to me yet.
Select_related already has a default maximum depth of 5, which already
meets the definition of "sensible" for many cases. I don't see any great
need to micromanage at that point by saying "perhaps 2 or 3 is better" --
we just pick a value and stick with it and 5 is the current value. We
could be here all day debating 2 or 3 or 5 or 7.
So the real issue is why this particular problem report is not respecting
the maximum depth of 5. If it is, then this becomes a proposal to change 5
to 3 and ... meh.
--
Ticket URL: <http://code.djangoproject.com/ticket/9554#comment:4>
Django <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
-~----------~----~----~----~------~----~------~--~---
