Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's a more direct answer to your question.</p> <p>In the second example, you are referring to a function that has to be in the global scope (i.e. a property of the <code>window</code> object).</p> <p>In the first example, you are referring to a property of the current view model.</p> <p>Yes, it's a subtle distinction, but it is an important one. If you use on-event attributes you can only refer to things that exist in the global scope. This means you have to put everything you want to access in the global scope, which leads to very messy code.</p> <p>If you use declarative bindings, the exact meaning of the bindings instead depends on the context.</p> <p>It helps to think about the HTML markup as more coincidental. What you are really looking at is structured access to the view model. Think of <code>with</code> and <code>forEach</code> as nested contexts and of the other bindings as their attributes. The relationship between the declarative bindings and the underlying HTML suddenly feels more like working with XSLT.</p> <p>The two examples <em>look</em> very similar. But the underlying concepts are vastly different and are what makes data binding so powerful and on-event attributes so obnoxious.</p> <p>The reason on-event attributes are frowned upon isn't just that they mix logic with structure. It's that they're a weak attempt to bolt arbitrary JavaScript code to HTML elements which prevents proper encapsulation of application logic. On-event attributes are low-level "hooks", bindings extend the behaviour of elements.</p> <p>All that said, it is likely possible to do the same horrible things people have done with on-event attributes by using declarative bindings. The difference is in what else you can do with them. You shouldn't always judge technologies by how they can be abused -- we're all adults here.</p>
    singulars
    1. This table or related slice is empty.
    1. POwhat is MVVM, and should we use it?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlan Plum
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFWIW, you likely won't find bindings terribly useful outside of single-page applications (read: web apps that heavily rely on JavaScript). They could be useful to bind simple widgets like datepickers, but it's hard to find a use case for normal websites that couldn't be easily replicated with CSS selectors and jQuery.
      singulars
      1. PO
      1. USAlan Plum
    2. COThanks Alan. That distinction makes a lot of sense. +1
      singulars
      1. PO
      1. USnicholas
    3. COBut doesn't the scope of the called javascript have more to do with how you organize your script than whether or not it should exist in the markup. I could just as easily do something like (to use a common jQuery syntax) onclick="$(this).data('myplugin').someFunction()" to call a scoped function using the onclick handler.
      singulars
      1. PO
      1. USnicholas
 

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