Re: Model Meta option default_related_name not setting related_query_name

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 nor the django docs 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+unsubscribe@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/e95b9048-717f-4ea6-b92c-4c7340f8b28f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.