Phil Freo

The relational 'Store' was designed to prevent having multiple instantiated objects with the same ID. Not sure why you need this, there might be some other way to workaround this...

Which version of bbr are you on? `_prepareModel` has just changed as of the most recent commits, to accomodate recent changes in that method in backbone.

A simpler way of saying it is that there's a race condition that can trigger the duplicate ID error to be thrown, in code as simple as: ``` users.fetch(); user...

The problem arises when the POST (creating an object) http response arrives _after_ another response (like a GET request) that already contains the newly created ID.

@PaulUithol does this make sense? I'm seeing this error frequently in this real-world situation: - background polling of parent model (`user.fetch()` every 5 seconds, which has nested `activities`) - user...

@PaulUithol if you don't have time to look at this bug, do you have any suggestions on how it should be fixed in BBR?

@maxwellmstein while I don't doubt there's some way to workaround this issue, it's not that simple because there are separate & independent views (and the fetching is happening with a...

It's harder because the fetch could happen before we even know there's going to be a save(), but you still have a race condition if the fetch response comes back...

After thinking about this one for a while, it seems like a fundamental design issue and there's no real way to fix it since you can't help but have 2...

I implemented what I described above. Basically I just avoid/pause background polling on models/collections when there's a "pending POST" that would create a new nested model that would show up...