EnsureSameTransaction for relationships: too restrictive?

Consider the following:

Child belongsTo Parent
Parent hasMany Childs
  • ember-data will always make sure that all records in a relationship are in the same transaction.
  • does it mean that there is no way to commit each Child independently? Indeed, to do this you would need to put each child in a different transaction, and it won’t work if they have the same parent (this parent can’t be in several transactions).

I don’t know if it is expected and/or not implemented or simply not something one should do (hence the post here instead of GitHub issues). But in this case, if we just want to commit the creation of an association (e.g. child1.set(‘parent’, parent1)), there is no real need to have parent1 moved to child1’s transaction, is there?

What is your take on this?