Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>To case n°1:</strong></p> <p>It depends, if you have for example a list of nine teasers where three teasers fill a line, I'd do it with one row:</p> <pre><code>&lt;ul class="row"&gt; &lt;li class="span4"&gt;&lt;/li&gt; &lt;li class="span4"&gt;&lt;/li&gt; &lt;li class="span4"&gt;&lt;/li&gt; &lt;!-- six more --&gt; &lt;/ul&gt; </code></pre> <p>If you're using the grid for layouting a form, I'd make a row for each label-input pair:</p> <pre><code>&lt;!-- one label-input pair does not fill the whole content width --&gt; &lt;form&gt; &lt;div class="row"&gt; &lt;label class="span3"&gt;&lt;/label&gt; &lt;input class="span5" /&gt; &lt;/div&gt; &lt;div class="row"&gt; &lt;label class="span3"&gt;&lt;/label&gt; &lt;input class="span5" /&gt; &lt;/div&gt; &lt;!-- and so on --&gt; &lt;/form&gt; </code></pre> <p>I think you shouldn't make a grid and put your content in the different grid cells to layout it, but build semantically correct markup and apply the grid to layout the content (tiny difference).</p> <p>PS: keep <a href="http://quirksmode.org/css/user-interface/boxsizing.html" rel="nofollow">box-sizing</a> in mind.</p> <p><strong>To n°2:</strong></p> <p>I don't quite get the idea there, if you're using the grid, you shouldn't apply left/right-margin to it. The grid depends on its horizontal margins to work properly... if you have to change this to match your frontend with the design it's probably not in the grid anymore.</p> <p>Update: I'd most certainly use your first example though, if you have smaller content. But use the correct grid span widths:</p> <pre><code>&lt;article class="row"&gt; &lt;header class="span12"&gt;&lt;/header&gt; &lt;div class="span10 offset1"&gt; &lt;div class="row"&gt; &lt;div class="span5"&gt;&lt;/div&gt; &lt;div class="span5"&gt;&lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/article&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBootstrap - Best practices on nesting - rows & spans
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSimon
    1. USSimon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBootstrap - Best practices on nesting - rows & spans
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COMore info about n°2 in 'my case' --> frenchdelicious.com/tmp.jpg
      singulars
      1. PO
      1. USSlake
    2. COOh well that's great, six spans in a 10 row :D. This actually isn't in your grid anymore, it will only "work" if you have a fluid grid because the spans then adjust inside whatever row you give them. But keep in mind that because of the percentage margins, you would have slightly smaller spaces between the spans than on the rest of the page...
      singulars
      1. PO
      1. USSimon
    3. COI see what you mean, but should i get rid of those spans and row & make it "by pure CSS" ?
      singulars
      1. PO
      1. USSlake
 

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