Databases
StackOverflow2013
Postsdbo
POdjango ModelForm save() method issue
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdjango ModelForm save() method issue
    primarykey
    data
    text
    <p>I have a model form: </p> <pre><code>class SnippetForm(ModelForm): class Meta: model = Snippet exclude = ['author', 'slug'] </code></pre> <p>and I want to be able to edit a particular instance by using this: </p> <pre><code>def edit_snippet(request, snippet_id): #look up for that snippet snippet = get_object_or_404(Snippet, pk=snippet_id) if request.user.id != snippet.author.id: return HttpResponseForbidden() if request.method == 'POST': form = SnippetForm(data=request.POST, instance=snippet) if form.is_valid(): form.save() return HttpResponseRedirect(snippet.get_absolute_url()) else: form = SnippetForm(instance=snippet) return render_to_response(SNIPPET_EDIT_TEMPLATE, {'form':form, 'add':False, 'user':request.user}, RequestContext(request)) </code></pre> <p>Notice that at the line </p> <p><code>form = SnippetForm(data=request.POST, instance=snippet)</code></p> <p>, I created a form that use the data supplied from the user, and bound it with the instance found using the primary key (received from the url). According to <a href="http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#the-save-method" rel="nofollow">django documentation</a>, when I call save() the existing instance should be updated with POSTED data. Instead, what I see is a new object is created and saved into the database. What went wrong? Thanks a lot. </p> <p>[Edit] This is really embarrassed. The code indeed has nothing wrong with it. The only thing that messed up the whole thing was the action I put in the template (as I use a same template for add and edit a snippet)....Thanks a lot for your help, really appreciate that.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USwakandan
    1. USwakandan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POdjango ModelForm save() method issue
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POdjango ModelForm save() method issue
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POdjango ModelForm save() method issue
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTry to debug it, I think the problem might be somewhere else.
      singulars
      1. POdjango ModelForm save() method issue
      1. USalex vasi
    2. COThere's nothing wrong with the code as posted - it should update the existing instance.
      singulars
      1. POdjango ModelForm save() method issue
      1. USDaniel Roseman
    3. COCan you explain what was wrong with the action? I think I may be having the same problem, but I'm not sure how the action would affect it.
      singulars
      1. POdjango ModelForm save() method issue
      1. USKobeJohn
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload