#27365: Fields suddenly not found.
-------------------------------------+-------------------------------------
Reporter: Brandon | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: FieldDoesNotExist | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin):
This looks like it could be a bug in Django, but I'm not sure. Is there
any chance you're defining Django models and not importing them in an
application's `models` module or package? This might explain what you're
seeing (in that case the answer is "don't do that").
--
Ticket URL: <https://code.djangoproject.com/ticket/27365#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/088.f41b54e5b0e08f9aa9057dbbaddf8693%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.