#8886: loaddata deserializes BooleanFields wrong for inheriting model
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone:
Component: Serialization | Version: 1.0
Resolution: | Keywords: loaddata
BooleanField
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
The problem here will stem from the ambiguity of having a field on the
child class that has the same name as a field on the base class. I'm
actually surprised that this isn't caught as a validation error in the
model definition, but given that it isn't, I can see how this would cause
problems for the serializer.
I'm uncertain if the solution here is to raise a validation error for
fields with ambiguous names, or to allow this kind of model and correct
the serialization. I can see arguments for both, but my gut reaction is
that the former is probably the right solution.
--
Ticket URL: <http://code.djangoproject.com/ticket/8886#comment:1>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
