#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:
Resolution: | Keywords: feature
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by orokusaki):
@russellm Why start with a diss on my code (that's called a tuple and
2-tuples, both very common in Django and Python). Read the title of this
ticket, and read my full example. It's about specifying recursion depth.
Not about excludes= or feilds=. That just happened to be added on half way
through. My version is not for specifying fields to be exported. Its to
represent which relationships (how deep) should be exported. Sure a class,
or a model Meta: may be the way to describe which format / fields get
exported, but my version merely says: "Export football team, and it's
related players, and their related records, and so on (the "related" being
models not fields).
--
Ticket URL: <http://code.djangoproject.com/ticket/4656#comment:18>
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.
