Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
fix(schema) declare timestamps as number to keep millisecond precision #3660
This changes that and makes all timestamps be stored with millisecond precision (no changes to the database are required, just that we replaced
However this is a breaking change: until now the
This change is required by #3622
My guess would be that this is because of the time order required by the targets?
An alternative would be to replace the UUID by a ULID. In a ULID, part of the randomness is sacrificed and replaced with a time stamp. The way this is done ensures that you can lexically sort based on the ULID, and get historical order.
A ULID is compatible (as a format) with UUID
But I don't know what the impact of that would be regarding breaking changes.