Databases
StackOverflow2013
Postsdbo
POWhy is Backbone model sending duplicate attributes to server on save?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is Backbone model sending duplicate attributes to server on save?
    primarykey
    data
    text
    <p>I'm writing a practice Backbone app, with Rails backend API, and I'm confused about the behavior of save on Backbone models.</p> <p>Let's say a Team has many Players, and I want to save a team with numerous players in a single POST.</p> <p>So in Rails I have:</p> <pre><code>class Team &lt; ActiveRecord::Base has_many :players accepts_nested_attributes_for :players end class Player &lt; ActiveRecod::Base belongs_to :team end </code></pre> <p>and for backbone client, I have a Player model and a Players collection defined (not shown)</p> <p>and then the containing Team model (NOTE: no Teams collection)</p> <pre><code>Demo.Models.Team = Backbone.Model.extend({ urlRoot: '/teams', defaults: { 'team_size': 12 }, initialize: function() { this.players = new Demo.Collections.Players()); }, toJSON: function() { var json = _.clone(this.attributes); json.players_attributes = this.players.map(function(player) { return player.toJSON(); }); return json; } } </code></pre> <p>When I examine my stringified JSON in the browser, everything looks good:</p> <pre><code>{"team_size":12, "players_attributes":[{"name":"Fred"},{"name":"Jim" },{"name":"Mark"}]} </code></pre> <p>Checking the server logs, the lone top level attribute ('team size') is repeated, once at the top level, and then repeated under a root key.</p> <pre><code>Started POST "/teams" for 127.0.0.1 at 2012-06-07 13:39:40 -0400 Processing by TeamsController#create as JSON Parameters: { "team_size"=&gt;12, "players_attributes":[{"name":"Fred"},{"name":"Jim" },{"name":"Mark"}]}, "team"=&gt;{"team_size"=&gt;12} } </code></pre> <p>I have a few questions:</p> <ol> <li><p>What's the best way to ensure the player_attributes are nested inside the root key? I (So that I can do a nested save inside TeamController, in the standard rails manner: (i.e. Team.create(params[:team]) ) I can accomplish this with some javascript hackery inside toJSON, but I'm guessing there's an easier, cleaner way.</p></li> <li><p>Is this standard, desirable behaviour? To send duplicates of attributes like this? I guess there's no harm, but it doesn't smell right.</p></li> <li><p>Am I not defining the url / urlRoot correctly or some such?</p></li> </ol> <p>thanks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNat Ritmeyer
    1. USdoublea
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBackbone sends exactly the result of toJSON(): `params.data = JSON.stringify(model.toJSON());`, so either your model contains such attributes or something strange on the server (there is waste closing brace in the log). Check the content of the http request in firebug to find out whom to blame.
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. USYaroslav
    2. COI've had this same problem with Backbone and Rails for a while... now I need to optimize and this is becoming obnoxious... any idea where it's coming from?
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. USwulftone
    3. COI think it's worth noting that in my case (and probably yours, too), backbone appears to be sending non-duplicated information. Firebug is telling me that the POST request sent to my server contained the correct, non-duplicated info. However, somewhere before it turns in to the ruby "params", it duplicates some stuff... why?
      singulars
      1. POWhy is Backbone model sending duplicate attributes to server on save?
      1. USwulftone
 

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