docs: update SQLite timestamp_ms example to allow millisecond defaults #448
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.
The current SQLite examples for setting the default value for a
timestamp_ms
column do not include the actual millisecond value of the current time, simply multiplying the UNIX timestamp in seconds by 1000. We can, however, obtain the millisecond value with the 'subsec' modifier to theunixepoch
function, which returns a float, which we can cast to an integer value:select unixepoch() * 1000, unixepoch('subsec'), CAST(unixepoch('subsec') * 1000 as INT);
One concern is this note from the SQLite Date/Time Function Docs:
But I don't think that would change the output.