Syncing from upstream OCA/web (19.0) - #1790
Merged
Merged
Conversation
… on the clone Extend the snapshot we re-apply after the onchanges to the relational types. Many2ones are copied as a new value object so both records don't share it, and many2manys through a SET command (and not LINK) so the copy ends up with exactly the same records as the source: this way we also drop the ones the onchange added on its own. One2manys can't be carried by that snapshot, as every sub-record has to be created on its own, so they are recreated line by line (recursively, for the nested ones): the copy's list is first emptied of whatever its onchanges generated, and then each line of the source is created, filled with its own snapshot and added to the list, the same way the core duplicates a record.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bt_gitbot