Quote:
Originally Posted by chaley
This is really a requirements issue. Are tags (text, is_multiple=True) merged, or do they overwrite?
|
Tags are merged.
Quote:
|
Are comments merged, or is one overwritten?
|
Comments are appended.
Quote:
|
What happens with series indices?
|
There is currently no independent test for series index. Series index is treated as a pair with series name. If the series name is empty in the destination, then both series name and index are written into the dest from the src. If the dest already has a series name, the index is never changed during merger.
Quote:
|
The equivalent custom fields should have the same processing.
|
Agreed, to the extent possible.
Quote:
|
My guess is that text (non-tag, is_multiple=False), bool, int, float, and date columns should overwrite. Make sense to you?
|
Yes - ("overwrite" empty field in dest, if src is not empty)
There seem to be 4 types of text
Text has:
- tag-like (merge, like tags)
- comments-like (append)
- plain-jane text (if dest is empty, fill from first src that is not empty)
- series-like (???)
As to series-like text, how does this differ from plain-jane text? I'm thinking of someone who has set up a secondary custom series in one field with an associated (in his mind) number field for ordering. It looks like even if the series-like text field is associated with an int or float, it would still be OK to treat the fields independently. As long as the user enters something in his number field when he enters something in the series-like text field, it wouldn't be overwritten and the pair wouldn't be decoupled.