New and revised timestamp docs #397
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
Current coverage is 88.39%@@ master #397 diff @@
==========================================
Files 18 18
Lines 1266 1284 +18
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 1118 1135 +17
- Misses 148 149 +1
Partials 0 0
|
|
|
||
| The result is that some timestamps can't be converted unambigously to a single UTC timestamp, but that only happens for leap seconds, and leap seconds are rare. (Only 26 had been inserted between 1972 and the end of 2015.) | ||
|
|
||
| **So long as you avoid the leap seconds, you can convert BigchainDB timestamps (Unix time timestamps) to UTC unambiguosly using any standard conversion tool or library function.** |
There was a problem hiding this comment.
unambiguosly --> unambiguously
|
👍 |
|
👍 |
|
Please don't merge this yet. I still want to clarify how to do (BigchainDB timestamp) --> UTC conversion for leap seconds. |
sbellem
pushed a commit
to sbellem/bigchaindb
that referenced
this pull request
Oct 24, 2016
…estamp-docs New and revised timestamp docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I revised the BigchainDB documentation on timestamps:
timestamp()function. It gets the Unix time, not UTC. The two are related, but different. In particular, UTC has leap seconds but Unix time doesn't.timestampexplanations in the page about data models (transactions, blocks, votes)