Add a flag to override model values

[rgreinho]

Types of changes

• New feature (non-breaking change which adds functionality)

Description

When updating models, it happens that we want to override the original
values.

Checklist:

• [] I have updated the documentation accordingly
• I have written unit tests

[mscarey]

Does the override flag always cause self to become a copy of other? If so, would it be clearer to use something like a .copy() method rather than a flag in the update method? I expected this flag to mean that fields in self would be overwritten only where other had truthy values for them.

[rgreinho]

Hmmm... good point. Now that you mention it, it does sound confusing a little. I'll think about it a bit more.

I expected this flag to mean that fields in self would be overwritten only where other had truthy values for them.

This is the behavior when the flag is set to False

[rgreinho]

@mscarey I update the logic with something which I think makes more sense: The empty values of one instance are updated with the non-empty values of another one.

As you said, if you want to update with all the values from another instance use the copy() function instead.

Let me know what you think of this one.