Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The RadioSelect widget will render its output by default into an unordered list.</p> <pre><code>#forms.py BEER = 0 WINE = 1 PREFERRED_DRINK_CHOICES = ( (BEER, 'Beer'), (WINE, 'Wine'), ) class DrinkForm(forms.Form): preferred_drink = forms.ChoiceField(choices=PREFERRED_DRINK_CHOICES, widget=forms.RadioSelect()) #views.py def test(request): form = DrinkForm(request.POST or None) if request.method == 'POST': if form.is_valid(): print 'form was valid' return render_to_response('test.html', {'form' : form}, context_instance=RequestContext(request)) #test.html &lt;form action="." method="post" enctype="multipart/form-data"&gt; &lt;ul&gt; &lt;li&gt; {{ form.name.label_tag }} {{ form.name }} {{ form.name.errors }} &lt;/li&gt; &lt;li&gt; {{ form.email.label_tag }} {{ form.email }} {{ form.email.errors }} &lt;/li&gt; &lt;li&gt; {{ form.preferred_drink.label_tag }} {{ form.preferred_drink }} {{ form.preferred_drink.errors }} &lt;/li&gt; &lt;li&gt; &lt;input type="submit" value="Submit" /&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/form&gt; </code></pre> <p>Will output:</p> <pre><code>&lt;form enctype="multipart/form-data" method="post" action="."&gt; &lt;ul&gt; &lt;li&gt; &lt;label for="id_name"&gt;Name&lt;/label&gt; &lt;input type="text" maxlength="50" name="name" id="id_name"&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="id_email"&gt;Email&lt;/label&gt; &lt;input type="text" id="id_email" name="email"&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="id_preferred_drink_0"&gt;Preferred drink&lt;/label&gt; &lt;ul&gt; &lt;li&gt; &lt;label for="id_preferred_drink_0"&gt; &lt;input type="radio" name="preferred_drink" value="0" id="id_preferred_drink_0"&gt; Beer&lt;/label&gt; &lt;/li&gt; &lt;li&gt; &lt;label for="id_preferred_drink_1"&gt;&lt;input type="radio" name="preferred_drink" value="1" id="id_preferred_drink_1"&gt; Wine&lt;/label&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/li&gt; &lt;li&gt; &lt;input type="submit" value="Submit"&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/form&gt; </code></pre> <p>That will render each radio choice on its own line. You'll probably need to add some CSS to get the rendering just the way you want, but that should get you the structure you need. Of course, you can shortcut writing the HTML by hand an just do...</p> <pre><code>&lt;form action="." method="post"&gt; &lt;ul&gt; {{ form.as_ul }} &lt;li&gt; &lt;input type="submit" value="Submit" /&gt; &lt;/li&gt; &lt;/ul&gt; &lt;/form&gt; </code></pre> <p>...but I prefer to write my HTML by hand.</p>
    singulars
    1. This table or related slice is empty.
    1. POIn a Django form, how do I render a radio button so that the choices are separated on the page?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBrandon
    1. USBrandon
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBut that still prints the two choices on adjacent lines, right? That's not what I'm trying to do. I want to have the two radio buttons widely separated, with blocks of fields underneath each one, as in my nascar/opera example.
      singulars
      1. PO
      1. USJohn Gordon
    2. COIf you write the HTML by hand, you can put additional fields or markup wherever you'd like. using form.as_ul will limit what you can do.
      singulars
      1. PO
      1. USBrandon
    3. COWhat's the syntax for rendering a single choice of a multi-choice radio button element? **{{form.preferred_drink}}** renders all the choices.
      singulars
      1. PO
      1. USJohn Gordon
 

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