Databases
StackOverflow2013
Postsdbo
POpassing object data through URL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpassing object data through URL
    primarykey
    data
    text
    <p>I know that I can pass object values through a URL pattern and use them in view functions. For instance:</p> <pre><code>(r'^edit/(?P&lt;id&gt;\w+)/', edit_entry), </code></pre> <p>can be utilized like:</p> <pre><code>def edit_entry(request, id): if request.method == 'POST': a=Entry.objects.get(pk=id) form = EntryForm(request.POST, instance=a) if form.is_valid(): form.save() return HttpResponseRedirect('/contact/display/%s/' % id) else: a=Entry.objects.get(pk=id) form = EntryForm(instance=a) return render_to_response('edit_contact.html', {'form': form}) </code></pre> <p>But how do I pass a value from a model field (other than "id") in the url? For instance, I have an abstract base model with a field "job_number" that is shared by child models "OrderForm" and "SpecReport". I want to click on the "job_number" on the order form and call the Spec Report for that same job number. I can create an </p> <pre><code>href="/../specifications/{{ record.job_number }} </code></pre> <p>to pass the info to the url, but I already know that this regex syntax is incorrect:</p> <pre><code>(r'^specifications/(?P&lt;**job_number**&gt;\w+)/', display_specs), </code></pre> <p>nor can I capture the job_number in the view the same way I could an id:</p> <pre><code>def display_specs(request, job_number): records = SpecReport.objects.filter(pk=job_number) tpl = 'display.html' return render_to_response(tpl, {'records': records }) </code></pre> <p>Is there an easy approach to this or is it more complicated than I think it is?</p> <p>the amended code is as follows:</p> <pre><code>(r'^specdisplay/?agencyID=12/', display_specs), </code></pre> <p>and:</p> <pre><code>def display_specs(request, agencyID): agencyID= request.GET.get('agencyID') records = ProductionSpecs.objects.filter(pk=id) tpl = 'display_specs.html' return render_to_response(tpl, {'records': records }) </code></pre> <p>not sure how to filter. pk is no longer applicable.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkjarsenal
    1. USkjarsenal
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POpassing object data through URL
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POpassing object data through URL
      1. USnikola
      1. VTFavorite
    3. VO
      singulars
      1. POpassing object data through URL
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think your only remaining problem is the url regex :) everything after the question mark (inclusive) has to go. Those are called GET parameters and aren't part of the matching stuff.
      singulars
      1. POpassing object data through URL
      1. USSwizec Teller
 

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