Database-specific Timestamp route#2864
Merged
Merged
Conversation
This interacts better with SpacetimeDB-cloud's routing code.
joshua-spacetime
approved these changes
Jun 13, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of Changes
Replaces
/unstable/timestampwith/v1/database/:name_or_identity/unstable/timestamp. This behaves the same as the previous version in SpacetimeDB-standalone (other than 404ing when passed a non-existent database name), but in SpacetimeDB-cloud allows the request to be routed to the node running the requested database's leader instance.BitCraft intends to use this for latency compensation somehow.
API and ABI breaking changes
The modified API is explicitly marked unstable and has not yet been included in a release.
Expected complexity level and risk
1
Testing