Never, ever, never, ever use timestamps for conflict resolution.
Conversation
I've had this argument so many times and decided timestamp at the time the change was actually made is good enough. Let's talk!
2
1
1
For sure if you can't share a clock within an acceptable delta of accuracy then yes it's a non starter
3
Another key idea: share a clock, but expose uncertainty, i.e. Spanner static.googleusercontent.com/media/research
1
Replying to
Ah, very interesting! Then you could make destructive merges only if the error bars don’t intersect…