We have two “regions” in our application. One in which the user can edit one model, and one in which they edit the children of that model.
We have two transactions and all commits/rollbacks are meant to be independent (ie: clicking “Save” in the children editing area shouldn’t effect the parent and vice versa).
This is resulting in:
All records in a changed relationship must be in the same transaction. You tried to change the relationship between records when one is in <DS.Transaction:ember765> and the other is in <DS.Transaction:ember766>
I understand the error, but I really want to use manage both the individual child records and there association with the parent in one transaction and the parent itself in another.
Can anyone think of a workaround? The only one that comes to mind would be to introduce an intermediate model that just sits between the children and the parent to ensure that the two transactions are totally independent. That doesn’t sound ideal…
Thanks in advance!