GitLab

On disk timestamps were using second resolution, while in memory and
sync representations were using microsecond. This meant that by round
tripping data to disk, the actual values would chance slightly. There
were several places that compared timestamps, and these difference did
no fix themselves, but rather resulted in repeated churn. The database
columns were already 64 bit integers, so this change doesn't even
modify the schema, just changes the format of data stored.

Bug: 775049
Change-Id: I03886d249c4b9195f20b897d309da6063db4bf6f
Reviewed-on: https://chromium-review.googlesource.com/806646
Commit-Queue: Sky Malice <skym@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521965}