docs(ASOF JOIN): Clarify timestamp control and precedence #197
Conversation
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
it was confusing before
|
🚀 Build success! Latest successful preview: https://preview-197--questdb-documentation.netlify.app/docs/ Commit SHA: b20a583
|
goodroot
reviewed
Jun 9, 2025
|
|
||
| :::caution | ||
| #### The Default Behavior: Implicit Timestamp Propagation |
There was a problem hiding this comment.
This title is slightly long.
Consider:
#### Default behaviour
As a default, QuestDB appies implicit timestamp propogation. This means that by default, an `ASOF JOIN` will...
There was a problem hiding this comment.
I wanted to be verbose here since I saw people getting this wrong and explicitly marking a column as a designated timestamp
Co-authored-by: goodroot <[email protected]>
goodroot
approved these changes
Jul 8, 2025
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.
Rework the
ASOF JOINtimestamp documentation to address the common misuse of thetimestamp(ts)syntax.The guide now clarifies that the designated timestamp is inherited by default. The standard method for joining on a different column is to use an
ORDER BYclause in a subquery, which implicitly sets a new timestamp for the join.The
timestamp(ts)syntax is now correctly framed as an expert-level performance hint, used only to assert a pre-sorted order on data that lacks a designated timestamp.