Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why to generate the HTML in PHP:</p> <ul> <li>JavaScript should define the behaviour, not the content.</li> <li>Creating in JavaScript requires more markup (multi-line strings aren't as easy as in PHP).</li> <li>It's harder to maintain if your HTML is generated in several places (PHP &amp; JS).</li> <li>You could use jQuery's DOM manipulation functions to create your HTML, but you're shooting yourself in the leg on the long run.</li> <li>It's faster to create the HTML at the server than on the browser (in computational sense).</li> <li>Looping is easier with PHP &ndash; it's easy to generate table markup.</li> <li>You retain some kind of combatibility if the user has JavaScript disabled if you output the markup on page load.</li> </ul> <p>Why to generate the HTML in jQuery:</p> <ul> <li>You'd save some bandwidth.</li> <li>Binding events might be simpler.</li> </ul> <p>So, I'm in favour of the first option, generating the HTML in PHP.</p> <hr> <p>Visual comparison of the two methods, creating a simple table. &nbsp;</p> <h3>Option 1, using PHP:</h3> <pre><code>// PHP $html = '&lt;table&gt;'; foreach($data as $row) { $html .= '&lt;tr&gt;'; $html .= '&lt;td&gt;&lt;a href="#" class="button"&gt;Click!&lt;/a&gt;&lt;/td&gt;'; $html .= '&lt;td&gt;'.$row['id'].'&lt;/td&gt;'; $html .= '&lt;td&gt;'.$row['name'].'&lt;/td&gt;'; $html .= '&lt;/tr&gt;'; } $html .= '&lt;/table&gt;'; echo $html; ?&gt; // jQuery $('#container').load('handler.php', function() { $('#container a.button').click(function() { // Do something }); }); </code></pre> <p>&nbsp;</p> <h3>Option 2, using jQuery:</h3> <pre><code>// PHP echo json_encode($data); // jQuery $.ajax({ url: 'handler.php', dataType: 'json', success: function(data) { var table = $('&lt;table /&gt;'); var len = data.length; for(var i = 0; i &lt; len; i++) { var row = $('&lt;tr /&gt;'); var a = $('&lt;a /&gt;').attr('href', '#').addClass('button'); row.append($('&lt;td /&gt;').append(a)); row.append($('&lt;td /&gt;').html(data[i].id); row.append($('&lt;td /&gt;').html(data[i].name); table.append(row); } table.find('.button').click(function() { // Do something }); $('#container').html(table); } }); </code></pre> <p>From a design / ease of coding / beauty point of view, I'd definitely say go with the PHP approach.</p>
    singulars
    1. This table or related slice is empty.
    1. POCreating HTML: PHP server-side vs. jQuery client-side
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTatu Ulmanen
    1. USTatu Ulmanen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCreating HTML: PHP server-side vs. jQuery client-side
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSome good points, but do you think it is really computationally faster for one server to do the work vs thousands of individual clients?
      singulars
      1. PO
      1. USuser113716
    2. CO@patrick, I was talking about the computational speed of one individual page load - the content will load faster if the HTML is created on the server. But of course it is always easier for the server if maximum amount of computations is transferred to the client.
      singulars
      1. PO
      1. USTatu Ulmanen
    3. COHmmm. If you want a comparison on equal grounds (and speed), you should build a string array in the javascript as well and just push the elements. At the end, join them and assign at once.
      singulars
      1. PO
      1. USAndras Vass
 

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