Update() destroys existing second-level relationships #211
Labels
Comments
|
Thanks for reporting this! We'll look into this issue as soon as we can. Because of the breaking changes, it can not be default behavior until 2.0, but we can add a |
|
NOTE: Reproduction case has been merged in |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like
Person.Save()saves only first level relationships, just like the README says. However, second-level relationships are destroyed if they already exist.The most inmediate fix would be to avoid this behaviour, making
Update()ignore second-level relationships instead of deleting them.As, in most cases, one would want to change just the relationship itself and not the whole depending object, a plain
Update()function may be appreciated.In fact, I think the case where you want to edit an object and its relatives in the same operation is fairly common for insertions, but relatively rare for updates. So making this new "plain update" the default behaviour and delegating the current "full update" operation to a different method might be worth considering.
The text was updated successfully, but these errors were encountered: