In that tutorial, time is recommended to be represented using a tuple of the different date components instead of a timestamp:
[year, month, day, hour, minute, seconds]
Isn’t that more costly in terms of disk space? The alternative will be to have a library that computes the “timestamp bounds” of a period of time. Now that I write about it, it seems complex.
How do other do represent timestamps in FoundationDB?