Jérôme Verstrynge <jvers...@gmail.com> writes: > You are making my point (lol). No matter what an application writes, > it should re-read its owns write for determinism for a given timestamp > when other application instances are writing in the same 'table'.
The timestamp is an ever increasing clock so I wouldn't expect two api calls from the same machine in the same thread to have the same timestamp. It is perfectly allowed behavior for the read value to not agree with the write value. Cheers, Chris Dean
