Skip to content

Document twap() designated-timestamp limitation#452

Open
mtopolnik wants to merge 1 commit into
mainfrom
mt_update-twap
Open

Document twap() designated-timestamp limitation#452
mtopolnik wants to merge 1 commit into
mainfrom
mt_update-twap

Conversation

@mtopolnik
Copy link
Copy Markdown
Contributor

twap() now rejects any timestamp argument other than the table's
designated timestamp. This updates the twap() reference page so the
timestamp parameter description states that requirement, framed as a
current limitation.

Companion to the questdb engine change that adds the rejection.

🤖 Generated with Claude Code

The twap() page said the timestamp argument could be any timestamp
column. twap() now rejects anything other than the table's
designated timestamp, because it relies on its observations already
being in ascending designated-timestamp order. Update the parameter
description to state this, framed as a current limitation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

🚀 Build success!

Latest successful preview: https://preview-452--questdb-documentation.netlify.app/docs/

Commit SHA: d9428ce

📦 Build generates a preview & updates link on each commit.

timestamp column.
- `timestamp` must be the table's
[designated timestamp](/docs/concepts/designated-timestamp/). As a current
limitation, `twap()` rejects a query that passes any other timestamp column
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would refrain from saying as a current limitation. We can just say it rejects a query that passes any other timestamp column. We can add a link to https://questdb.com/docs/query/functions/timestamp/ if the user needs to see how to convert a non-designated timestamp column into the designated timestamp for the query

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants