Paul Uithol
Paul Uithol
Because at that point, updates should already have been merged into the model - through the `_prepareModel`->`findOrCreate` route. Do you maybe have an example where that doesn't happen? Removing the...
What does this fix, exactly? Can you show that, possibly though a test case?
Could you try to translate what you're seeing to a jsFiddle? Sort of sounds to me like there's a data problem _somewhere_ in there - but I can't figure out...
This doesn't really sound specific to backbone-relational? Seems more like the default backbone implementation of `fetch` doesn't play nice with what you're trying to achieve. In your case, I would...
Btw, I'm also working on a better implementation for lazy loading; sounds like that may be at the core of your problem? See #467 .
Well, the reason it isn't in there right now is that it's quite complicated to get this 'right', especially with regards to all the events flying around (which is already...
I've never had any issue with this. Did you experience this yourself? Do you have a testcase or something else that shows this behavior?
Yeah, not using a RelationalModel should disable caching.. and that's about the only way. Relations wouldn't function without it.
There's a `package.json` in there now, along with a `bower.json`. That makes it NPM installable I think? And it still functions as a django app as well.
How would that generate a duplicate id exactly? I'm assuming `user.save()` will generate a new one?