#6773: Confusing error when ForeignKey lookup fails while serializing
-------------------------------------+-------------------------------------
Reporter: kcarnold | Owner:
Type: | Status: closed
Cleanup/optimization | Component: Core
Milestone: | (Serialization)
Version: 1.2-alpha | Severity: Normal
Resolution: needsinfo | Keywords: dumpdata exception
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 1
Needs documentation: 1 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => needsinfo
* stage: Fixed on a branch => Design decision needed
Comment:
The answers you seek can be partially found by reading the ticket history.
The ticket *was* DDN until it was marked "Fixed on a branch" by an
anonymous user (who also marked it for milestone 1.3). Since the anonymous
person didn't give any explanation, you can probably assume that that
update was spam. That means the ticket is waiting on a design decision.
A patch has been provided; that patch isn't a diff against trunk, and it
doesn't include tests. It also introduces a new management command, but
includes no documentation for that management command. Assuming that the
patch is the right fix, the patch isn't ready for trunk because of these
missing elements.
However, I'm not convinced the patch is the right approach. We already
have a "find the errors" command -- it's called validate. I don't see the
use case for an additional management command to catch serialization
errors. In any case, blank=True without null=True shouldn't pose a
serialization problem, but the reporter doesn't provide a clear test case
to validate the problem they describe.
Given that this problem was reported 3 years ago, there have been many
improvements in serialization error reporting since that time, and many
edge cases caught in serialization since then, I'm going to close this
needsinfo. If someone can verify that this is still a problem, feel free
to reopen, providing a specific reproduction test case.
--
Ticket URL: <https://code.djangoproject.com/ticket/6773#comment:16>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
