Model in multiple collections

[jmcgdz]

I know there has been a lot of talk around this, but I cannot find a solution for my situation.

I'm not sure if I'm using bb relational as it was intended.

My use case is:

[
  {
    "id": "dashboard_container_uuid_1",
    "dashboards": [
      {
        "id": "dashboard_uuid_1",
        "widgets": []
      },
      {
        "id": "dashboard_uuid_2",
        "widgets": []
      }
    ]
  },
  {
    "id": "dashboard_container_uuid_2",
    "dashboards": [
      {
        "id": "dashboard_uuid_3",
        "widgets": []
      },
      {
        "id": "dashboard_uuid_4",
        "widgets": []
      }
    ]
  },
  {
    "id": "dashboard_container_uuid_3",
    "dashboards": [
      {
        "id": "dashboard_uuid_2",
        "widgets": []
      },
      {
        "id": "dashboard_uuid_4",
        "widgets": []
      }
    ]
  }
]

And my issue is that the 'dashboard_container_uuid_3' instance has an empty dashboards collection.

I'm assuming this is because it is trying to create duplicate 'dashboard' models since '2' and '4' are already in previous 'dashboard_container', but I can't find a clean solution to make this work.

[philfreo]

I don't think there should be any problem with this. Want to post your relations code from both models? You may also want to fiddle with the reverseRelations settings http://backbonerelational.org/#relations-reverseRelation

[rodneyrd]

@jmcgdz I am actually facing the same problem with nested collections that contain the same model id. Models with same ids aren't duplicated into nested collections.
Still trying to figure out a work around, problably using a many-to-many relation will solve this. Please let me know if you could get it working.

[rodneyrd]

@jmcgdz I made it working using a many-to-many relationship. So in your example you can finally have same "dashboard ids" into different "dashboard_container_uuid". Take a look at this fiddle many-to-many relations example that helped me a lot since BB relational doesn't have a proper documentation for it: http://jsfiddle.net/mmacaula/XaESG/2/

[jameshowe]

I've got a similar problem, in my case the models are going into the different collections but they are being overridden by the first model to be created.

Maybe I'm oversimplifying things here but why can't we just have a flag against a RelationalModel that determines whether or not we want it to be cached? e.g.

DuplicateModel = new Backbone.RelationalModel.extend({
    singleton: false // don't cache
});

This would help me a lot as for the most part I am only using BBR for the sub-model type binding.