﻿id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 4656,Allow In-depth serialization by specifying depth to follow relationship,jay.m.martin@…,nobody,"It would be nice to be able to specify whether to traverse relationships when calling serialize. For example, say you had 2 models defined as: {{{ class Reporter(models.Model): first_name = models.CharField(maxlength=30) last_name = models.CharField(maxlength=30) email = models.EmailField() class Article(models.Model): headline = models.CharField(maxlength=100) pub_date = models.DateField() reporter = models.ForeignKey(Reporter) }}} If you serialize a queryset from the Article model, the result will only contain the primary keys of the related Reporter models. I think an additional argument specifying the maximum depth to traverse relationships (similar to select_related). So if you pass 1 as the depth in the above example, the result will contain the complete deserialization of the related Reporter objects as well. ",New feature,new,Core (Serialization),,Normal,,feature,mattimustang@… datavortex@… django@… tosters@… tomchristie kmike84@… hv@…,Accepted,0,0,0,1,0,0