On 04/18/2011 11:16 AM, Carl Meyer wrote:
By "just this" I presume you actually mean just the second half of what
you quoted ("explicitly set to False")? In other words, you're proposing
to make use_for_related_fields work as advertised, but make it default
to True instead of False?
Not exactly… I mean that when use_for_related_fields is set explicitly
Django should respect it. Right now, as I understand from your first
mail, it doesn't work as False when set to False. So I agree that this
should definitely be fixed.
What I was saying is that when this attribute is not set current
behavior does make sense:
- use default manager as a base for *_set managers
- use pure manager as a base for OneToOne and parent lookups
However it can't be described with neither "False by default" nor "True
by default". I think it's fine and we could just thoroughly document
this behavior.
P.S. Sorry for being sloppy with my first reply…
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
