#33590: Related object is not resolved
----------------------------------+--------------------------------------
Reporter: Stefan de Konink | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Matthew Schinckel):
I've been working with Stefan to try to figure out what is going on in
IRC.
It appears that something about the Django SQL infrastructure is changing
the results (or maybe the query) so that one column is getting set to NULL
(by the database) rather than having the value.
I'm not sure that the title of this bug accurately reflects the problem
yet though.
--
Ticket URL: <https://code.djangoproject.com/ticket/33590#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017faa045d7c-905e8daf-7d00-457c-8c75-301af2a8d34d-000000%40eu-central-1.amazonses.com.
