9.1.0 release roundup #246
Conversation
|
🚀 Build success! Latest successful preview: https://preview-246--questdb-documentation.netlify.app/docs/ Commit SHA: 7c1b397
|
| You can work around this limitation by using CTEs or subqueries: | ||
|
|
||
| ```questdb-sql | ||
| -- CTE |
There was a problem hiding this comment.
should we make this query demoable or is it too much in an info block?
There was a problem hiding this comment.
I'll add the demo tag, we can see how it looks
| | :--------------- | | ||
| | 49.5442334742831 | | ||
|
|
||
| ## mode |
There was a problem hiding this comment.
please, move before nsum to keep alphabetical order
There was a problem hiding this comment.
I thought this originally too, but we don't respect alphabetical order - for example first/last is a single entry. I'm all in favour for splitting them and making them alphabetical though. Ideally we need a smarter sort by usage i.e. predicate aggregates (first/last/min/max) versus reducation aggregate (sum, avg etc.)
| | A | alpha | | ||
| | B | beta | | ||
|
|
||
|
|
There was a problem hiding this comment.
Should we add a demoable query? this one is nice
select symbol, mode(price)
from trades
where timestamp in today()
There was a problem hiding this comment.
Perhaps mode(price) is not ideal, because of precision. Maybe mode(side) i.e. were there more buys and sells for each symbol?
Closes #170