I followed the dev. manual https://apple.github.io/foundationdb/api-c.html#c.FDBMutationType,
and tried to get as many concurent transactions as I can to produce non-zero ending bytes of
versiontimestamp, I always got
versiontimestamp s ended with 0x0000.
I am wondering under what kinds of scenarios
SET_VERSIONSTAMPED_VALUE will result in a
versiontimestamp that does not end with 0x0000?
Is it safe for my app. to ignore the trailing 2 bytes and use an int64 for the first 8 bytes to represent a globally monotonic unique id? If not, what’s the chance that I will get 2 int64 with the same value?
I’ve searched the forum and read lots of docs, but nothing was found to help resolve my question, so I start a new topic to ask for help.