StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20793936
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-27T02:29:45.710
FavoriteCount
0
LastActivityDate
2013-12-27T02:29:45.710
LastEditDate
LastEditorUserId
0
OwnerUserId
540644
ParentId
20791165
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Use a <a href="https://docs.djangoproject.com/en/1.6/topics/forms/modelforms/" rel="nofollow"><code>ModelForm</code></a> instead of a regular <code>Form</code>. A <code>ModelForm</code> can be associated with an instance, which is the used to prepopulate the form. If you want to update both the <code>User</code> and the profile, you can use two <code>ModelForm</code>s in one view. For example: <pre><code>class UserModelForm(forms.ModelForm): repassword = ... # additional fields that have no represenation in the model class Meta: model = User fields = ["username", "password", ] # ... def clean(self): # ... your validation logic class ProfileForm(forms.ModelForm): class Meta: model = YourProfileModel fields = [] # ... </code></pre> Then use both in the view: <pre><code>def usermodify(request, user): # mod_user = ... user_form = UserModelForm(request.POST or None, instance=mod_user) profile_form = ProfileForm(request.POST or None, instance=mod_user.get_profile()) if user_form.is_valid() and profile_form.is_valid(): user_form.save() # this saves to the associated mod_user, as passed via the `instance` argument profile_form.save() # ... redirect etc. return render(..., {'user_form': user_form, 'profile_form': profile_form}) # pass both forms to the template </code></pre> In the template, put both forms inside of one <code><form></code> tag. Be sure that they don't have conflicting field names, or <a href="https://docs.djangoproject.com/en/dev/ref/forms/api/#prefixes-for-forms" rel="nofollow">use a <code>prefix</code>.</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSet form's default values from existing objects in Django
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsk1p
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
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.