This bug is *still* occurring... And seems to do so in waves. But after
fighting it again and again, something struck me.
The bug always occurs here: django/db/models/fields/reverse_related.py in
get_related_field at line 244
So always in this function:
def get_related_field(self):
"""
Return the Field in the 'to' object to which this relationship is
tied.
"""
field = self.model._meta.get_field(self.field_name)
if not field.concrete:
raise exceptions.FieldDoesNotExist("No related field named '%s'"
%
self.field_name)
return field
But specifically is it occurring *because* self.model._meta.get_field(self.
field_name) is not returning a field (e.g. django.db.models.fields.*).
Somehow self.model._meta.get_field(self.field_name) is returning a
OneToOneRel object.
Should self.model._meta.get_field(self.field_name) ever return *anything*
other than some django.db.models.fields.* object?
Cheers!
--Brandon
--
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/15ba1e2c-f250-47c2-8926-795463a93620%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
