sot/timelines — comment on commit a0d477fd23bcddf6b63307800e2d531b2c017534
File: update_load_seg_db.py line 485
By jeanconn:

> This logic here is still a bit problematic. I believe that it works now
> for the current SOSA configuration. However, in general `datestart` is
> not a unique key here and so previously matching records could (in
> theory, not in practice) be selected.

Yes. I was conscious of this, but thought that the datestart-based match
might reduce overall confusion (if either of a pair is modified, even the
member that doesn't change will be re-inserted). However, I cannot figure
out any test case that makes the datestart wiping *better* than the i_diff
range choice.

-Jean