Hi Alejandro, This looks like a bug and overlook to me but as Tim pointed out simply changing it would be backward incompatible at this point.
If we were to fix this issue we would need to deprecate the actual behavior first. The deprecation path would involve raising a warning when the actual related_query_name is referenced (e.g. through Queryset.filter(), annotate(), ...) if default_related_name was defined and then switch to the new behavior once the deprecation period end. If you are really motivated into fixing this please file a new ticket <https://code.djangoproject.com/newticket> to track your effort. Simon Le samedi 14 novembre 2015 10:03:57 UTC-5, Tim Graham a écrit : > > I guess it would be backwards incompatible if we changed the behavior now, > wouldn't it? > > On Friday, November 13, 2015 at 1:40:27 PM UTC-5, Alejandro Do Nascimento > wrote: >> >> django...@googlegroups.com >> >> Hello, >> >> I have a doubt, In a model I'm using the Meta option * >> default_related_name*, this sets the related manager but it doesn't set >> the *related_query_name* as using related_name in a field would do, is >> this a bug or the intended functionality? >> >> Neither the new feature ticket >> <https://code.djangoproject.com/ticket/22778> nor the django docs >> <https://docs.djangoproject.com/en/1.8/ref/models/options/#default-related-name> >> >> say anything about it. >> >> Thx >> >> -- >> AD.N >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/70bd0886-6161-4840-bd91-afc4377a47bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
