#4656: Allow In-depth serialization by specifying depth to follow relationship
---------------------------------------------+------------------------------
Reporter: jay.m.mar...@gmail.com | Owner: nobody
Status: new | Milestone:
Component: Serialization | Version: SVN
Resolution: | Keywords: feature
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by orokusaki):
@Matthew Flanagan I would prefer to use either. I mean, it would be nice
if it operated like model forms in that if you say excludes=('myfield',),
then it does all but that one, and if you say includes=('myfield',), it
only does that one. I especially think includes is very important because
it's more explicit. If you have a big model and an actively changed API,
and you only have excludes, then what happens when somebody adds a new
"secure" field to the model? It suddenly shows up in the output.
--
Ticket URL: <http://code.djangoproject.com/ticket/4656#comment:15>
Django <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 django-upda...@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.
