Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have the very same issue while I'm writing my Backbone application. Having to deal with embedded/nested models. I did some tweaks that I thought was a quite elegant solution.</p> <p>Yes, you can modify the parse method to change a attributes around in the object, but all of that is actually pretty unmaintainable code IMO, and feels more of a hack than a solution.</p> <p>Here's what I suggest for your example:</p> <p>First define your Layout Model like so.</p> <pre><code>var layoutModel = Backbone.Model.extend({}); </code></pre> <p>Then here's your image Model:</p> <pre><code>var imageModel = Backbone.Model.extend({ model: { layout: layoutModel, }, parse: function(response){ for(var key in this.model) { var embeddedClass = this.model[key]; var embeddedData = response[key]; response[key] = new embeddedClass(embeddedData, {parse:true}); } return response; } }); </code></pre> <p>Notice that I have not tampered with the model itself, but merely pass back the desired object from the parse method.</p> <p>This should ensure the structure of the nested model when you're reading from the server. Now, you would notice that saving or setting is actually not handled here because I feel that it makes sense for you to set the nested model explicitly using the proper model.</p> <p>Like so:</p> <pre><code>image.set({layout : new Layout({x: 100, y: 100})}) </code></pre> <p>Also take note that you are actually invoking the parse method in your nested model by calling:</p> <pre><code>new embeddedClass(embeddedData, {parse:true}); </code></pre> <p>You can define as many nested models in the <code>model</code> field as you need.</p> <p>Of course, if you want to go as far as saving the nested model in its own table. This wouldn't be sufficient. But in the case of reading and saving the object as a whole, this solution should suffice.</p>
    singulars
    1. This table or related slice is empty.
    1. PONested Models in Backbone.js, how to approach
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USArslan Ali
    1. USrycfung
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONested Models in Backbone.js, how to approach
      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. COThis is nice.. should be the accepted answer as its far cleaner than the other approaches. Only suggestions I'd have is to capitalize the first letter of your classes that extend Backbone.Model for readability.. i.e. ImageModel and LayoutModel
      singulars
      1. PO
      1. USStephen Handley
    2. CO@StephenHandley Thanks for the comment and your suggestion. For the information, I'm actually using this in the context of requireJS. So, to answer to the capitalization matter, the var 'imageModel' is actually returned to requireJS. And the reference to the model would be encapsulated by the following construct: `define(['modelFile'], function(MyModel){... do something with MyModel})` But you're right. I do make it a habit to reference the model by the convention you suggested.
      singulars
      1. PO
      1. USrycfung
    3. COYour code has "return data"; what does "data" refer to?
      singulars
      1. PO
      1. USBobS
 

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