Skip to content

Document twap() designated-timestamp limitation #452

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.

Sign up for GitHub

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

Open
mtopolnik wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −3
Open

Document twap() designated-timestamp limitation #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions documentation/query/functions/aggregation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1659,9 +1659,10 @@ Supports `SAMPLE BY` with `FILL` modes.
#### Parameters

- `price` is any numeric value.
- `timestamp` is a `timestamp` value. This is typically the table's
[designated timestamp](/docs/concepts/designated-timestamp/) but can be any
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

@javier javier May 26, 2026

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

or expression.

#### Return value

Expand Down
Loading