Redefine Skeleton's changedate

[sveneberth]

Ensure we have a trustworthy changedate, which should only be changed, if the values in the skeleton has been changed by the user. Otherwise keep the changedate the same, even after a .toDB().

Some notes from the brainstorming

• trigger only by real changes from a user (not from e.g. a updateRelations task)
• Create hashes for comparison?
• Consider datastore changedate?
• Updatemagic / Changedate only on real changes

[phorward]

Relates to #785

[phorward]

Fixed by #785

[sveneberth]

which should only be changed, if the values in the skeleton has been changed

I don't think this is solved. We update the changedate on every toDB(), but also if there were no changes. Furthermore I don't know what happens if changedate isn't part of a subskel.

[phorward]

This could be resolved together with #478, as there is a comparison of the old and new dataset, and also an ignore list which skips specific bones when changed (e.g. changedate 😜)

[phorward]

viur-meeting: We should think about a second field for this date.

Scribble:

• add_date
• edit_date
• write_date