StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORegistration of an extended user through POST request
primarykey
Id
19547761
data
AcceptedAnswerId
19560598
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-23T16:54:23.120
FavoriteCount
0
LastActivityDate
2013-11-01T11:02:09.820
LastEditDate
LastEditorUserId
0
OwnerUserId
1503534
ParentId
0
PostTypeId
1
Score
0
ViewCount
194
LastEditorDisplayName
text
Body
I am using Django v1.7dev with the Django Rest Framework v2.3 I have extended the user Class as follows: <pre><code>class UserProfile(models.Model): user = models.OneToOneField(User) gang = models.ForeignKey('Gang', related_name='gangsters') def __unicode__(self): return self.user.username User.profile = property(lambda u: UserProfile.objects.get_or_create(user=u)[0]) </code></pre> I have also created a User serializer endpoint (which does not show the password when I sent a GET request, but accepts it when I send a post, with the purpose of using it for registration: <pre><code>class UserSerializer(serializers.ModelSerializer): class Meta: model = User fields = ('id', 'username', 'password', 'email') def restore_object(self, attrs, instance=None): user = super(UserSerializer, self).restore_object(attrs, instance) user.set_password(attrs['password']) return user def to_native(self, obj): ret = super(UserSerializer, self).to_native(obj) del ret['password'] return ret </code></pre> I'd love to extend the serializer to include also the gang parameter. Something similar to <pre><code>gang = serializers.Field(source='profile.gang') </code></pre> but writable instead of ReadOnly, so that when I register a user I can insert also the gang, possibly in an atomic way. What is the best approach in this case? I have tried to play a bit with other fields types, but unsuccessfully till now. At the moment I am sending two separate post (one for User and one for UserProfile, but I bet there is a better way...)
Tags
<django><django-rest-framework>
Title
Registration of an extended user through POST request
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsyymza
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.