On Fri, Oct 23, 2015 at 3:27 PM, Gagaro <gagar...@gmail.com> wrote:
> However, I still have a question. The reverse relation is wishlist_set by
> default. Why is Django bothered if the attribute is name wishlist (I would
> understand if I named my attribute wishlist_set)?
The message doesn't mention the reverse relation names that conflict,
it mentions the names of *fields* whose relation names would conflict.
> Reverse query name for 'Wishlist.user' clashes with field name
> 'User.wishlist'.
> HINT: Rename field 'User.wishlist', or add/change a related_name argument to
> the definition for field 'Wishlist.user'.
'Wishlist.user' and 'User.wishlist' are the names of the fields being
discussed. The meaning might be clearer with some added words:
The reverse query name for the field 'Wishlist.user' clashes with
the field 'User.wishlist' - they are both ''wishlist_set'.
HINT: Rename field 'User.wishlist', or add/change a related_name
argument to the definition for field 'Wishlist.user'.
Cheers
Tom
--
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/CAFHbX1LWG0Rc0kKU-SwLUmfzc%2B3ATEtYSj%2B18VwQ47Af5o-g2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
