Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add ns precision support to time values #2940

Merged
merged 2 commits into from
Aug 21, 2024

Conversation

AndrewSisley
Copy link
Contributor

Relevant issue(s)

Resolves #2927

Description

Add nanosecond precision support to time values.

Was previously only second precision, which is not particularly useful for many applications (such as createdAt timestamps used to allow multiple similar documents to be created within the same second).

@AndrewSisley AndrewSisley added bug Something isn't working area/db-system Related to the core system related components of the DB labels Aug 21, 2024
@AndrewSisley AndrewSisley added this to the DefraDB v0.13 milestone Aug 21, 2024
@AndrewSisley AndrewSisley requested a review from a team August 21, 2024 17:31
@AndrewSisley AndrewSisley self-assigned this Aug 21, 2024
Copy link

codecov bot commented Aug 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.37%. Comparing base (601a92a) to head (0c8e4d9).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #2940      +/-   ##
===========================================
+ Coverage    79.30%   79.37%   +0.08%     
===========================================
  Files          326      326              
  Lines        24856    24860       +4     
===========================================
+ Hits         19710    19732      +22     
+ Misses        3731     3720      -11     
+ Partials      1415     1408       -7     
Flag Coverage Δ
all-tests 79.37% <100.00%> (+0.08%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
client/document.go 72.26% <100.00%> (+0.24%) ⬆️
client/value.go 95.24% <100.00%> (ø)

... and 11 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 601a92a...0c8e4d9. Read the comment docs.

Was previously only second precision, which is not particularly useful for many applications (such as createdAt timestamps used to allow multiple similar documents to be created within the same second).
Copy link
Collaborator

@fredcarle fredcarle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for taking care of this. Not sure why we didn't do this from the start.

@AndrewSisley AndrewSisley merged commit a4029a9 into sourcenetwork:develop Aug 21, 2024
36 of 39 checks passed
@AndrewSisley AndrewSisley deleted the 2927-datetime-ms branch August 21, 2024 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/db-system Related to the core system related components of the DB bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DateTime milliseconds do not appear to contribute to docID
2 participants