liveBook · Manning

Edit mode

As explained in Django in Action

Edit mode is the operating mode in which a form view modifies an existing object.

Edit mode lets one form view update an existing object instead of creating a new one. The view receives the object's ID, fetches the owned record, and uses it to prepopulate the form. Add mode uses the same view without an ID, keeping similar behavior in one place. section 7.2.5

A Django-style implementation follows this request flow:

  • Use separate add and edit routes that call the same view; the edit route supplies an integer object ID. section 7.2.5

RiffMates seeking ads

A `seeking_ad(request, ad_id=0)` view treats `ad_id=0` as Add mode and another ID as Edit mode. The edit URL is `edit_seeking_ad/<int:ad_id>/`, and an Edit link appears only for the ad owner.

How Django in Action covers it

How deep it goes
Explains routes, IDs, object lookup, GET handling, and POST binding, but does not detail validation or saving.
Examples
Uses RiffMates seeking ads, separate add and edit URLs, owner-filtered lookups, and an owner-only Edit link.
What it assumes
Assumes forms, models, URLs, and ORM IDs, while introducing shared add/edit views from familiar Python function arguments.
What you can do after
Apply it via Django ModelForms to prepopulate and submit updates for existing user-owned records.
How it connects
Connects ModelForm instances with URL routing, ORM object lookup, HTTP methods, and object ownership.
Cover of Django in Action
liveBookmanning.com
Read Django in Action on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Django in Action. The section links point to the parts of the book it draws on.