Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>this</code> changes meaning as you step into new nested functions. It does <strong>not</strong> change meaning when you call <code>$()</code> to create a new element. </p> <p>So immediately inside of</p> <pre><code>$.each(obj, function(index, dataObj) { </code></pre> <p><code>this</code> is the current object over which your looping. Once you get here:</p> <pre><code>.live("click",function(event) { // &lt;------ inside of nested function openVideo($(event.target).data(dataID)); }) </code></pre> <p><code>this</code> is the element on which you clicked. </p> <p>But calling </p> <pre><code> $("&lt;li/&gt;",{data:{dataID:dataObj.id},text:dataObj.name}) </code></pre> <p>to create a new <code>li</code> element does <strong>not</strong> set <code>this</code> to the newly created element. </p> <hr> <p>Also, if you want to save the meaning of <code>this</code> even inside of nested functions, the standard way is to save it to a new variable.</p> <pre><code>$.each(obj, function() { var self = this; </code></pre> <p>Now <code>self</code> can be used instead of <code>this</code> as the item you're currently "on" anywhere in your loop, even in nested function handlers. Or you can pass index and dataObjects to the each function - same effect. </p> <p><strong>EDIT</strong></p> <p>As a comment pointed out, you're using live incorrectly. If you're using jQuery 1.7, you'll want:</p> <pre><code>$(document).on("click", "li", function(event) { openVideo($(this).data(dataID)); }); </code></pre> <p>in your <code>document.ready</code> handler. If all li's that will be clicked will be in a certain div, than select on that div instead of <code>document</code>. If you don't want this click handler to apply to all li's, but only some, then decorate all the li's you want this click handler to apply to with a css class, then instead of passing the filter "li" to <code>on</code>, you'd pass <code>li.yourClass</code> </p>
    singulars
    1. This table or related slice is empty.
    1. POWhy is my 'this' not changing context inside inner jQuery each loop?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAdam Rackis
    1. USAdam Rackis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy is my 'this' not changing context inside inner jQuery each loop?
      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. COproblem is it isn't changing to the freshly created LI element, which I'm chaining the subsequent methods to...
      singulars
      1. PO
      1. USbodine
    2. CO+1 for correctly explaining the effect of scope on 'this'.
      singulars
      1. PO
      1. USPrisoner ZERO
    3. COSo, I'm still unclear as to why my chained methods are using `dataObj` instead of the jQuery object created (and returned by) `$("<li/>",{data:{dataID:dataObj.id},text:dataObj.name})`. Inside a jQuery method chain isn't `this` supposed to be the selector object at the beginning of the chain?
      singulars
      1. PO
      1. USbodine
 

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