-
Notifications
You must be signed in to change notification settings - Fork 10
Add Timestamp
to the SDK, moving it out of client_api
#114
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
Conversation
|
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything here makes sense.
Companion to SpacetimeDB#1836
From SpacetimeDB 072c2ea3a32a6cf6d05ecf1ac9c9b54a4f95e340: Prioritize BSATN and BFLATN compat with 0.12 Timestamp and TimeDuration store `micros: i64`, not `nanos: i64`. This means that old commitlogs and snapshots should still be compatible, assuming they don't include timestamps greater than `i64::MAX`, as previously we used `micros: u64`. This seems unlikely.
2e71446
to
9065fb9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM. I ended up reimplementing most of this in a future PR so I am quite familiar with it.
Description of Changes
Companion to SpacetimeDB#1836.
Based off #109
API
Type of
ReducerEvent.timestamp
is changed, methods onTimestamp
are different, and WS API is updated.Requires SpacetimeDB PRs
List any PRs here that are required for this SDK change to work
Timestamp
a special SATS type SpacetimeDB#1836