-
Notifications
You must be signed in to change notification settings - Fork 116
Fix prev/next expression examples #3637
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.
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
intermittentnrg
wants to merge
6
commits into
timescale:latest
Choose a base branch
from
intermittentnrg:fix-prev-next
base: latest
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1efb252
Fix prev/next expression examples
intermittentnrg cebc523
Merge branch 'latest' into fix-prev-next
billy-the-fish 3692895
Merge branch 'latest' into fix-prev-next
billy-the-fish dd3f7bd
Merge branch 'latest' into fix-prev-next
billy-the-fish f8e6ee8
Merge branch 'latest' into fix-prev-next
billy-the-fish 6842a81
Merge branch 'latest' into fix-prev-next
billy-the-fish File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -75,17 +75,19 @@ to fill gaps at the beginning of the queried time range. Note that the | |||||
|
||||||
```sql | ||||||
SELECT time_bucket_gapfill('1 day', time) AS day, | ||||||
device_id, | ||||||
locf( | ||||||
avg(value), | ||||||
( | ||||||
SELECT value | ||||||
FROM metrics | ||||||
WHERE time > '2021-12-31 00:00:00+00'::timestamptz | ||||||
ORDER BY time ASC | ||||||
FROM metrics m2 | ||||||
WHERE time < '2021-12-31 00:00:00+00'::timestamptz AND | ||||||
m.device_id=m2.device_id | ||||||
ORDER BY time DESC | ||||||
LIMIT 1 | ||||||
) | ||||||
) as value | ||||||
FROM metrics | ||||||
FROM metrics m | ||||||
WHERE time > '2021-12-31 00:00:00+00'::timestamptz | ||||||
AND time < '2022-01-10 00:00:00-00'::timestamptz | ||||||
GROUP BY day | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
@@ -148,24 +150,27 @@ arguments to `interpolate` to extrapolate the missing values starting and ending | |||||
|
||||||
```sql | ||||||
SELECT time_bucket_gapfill('1 day', time) AS day, | ||||||
device_id, | ||||||
interpolate( | ||||||
avg(value), | ||||||
( | ||||||
SELECT (time, value) | ||||||
FROM metrics | ||||||
WHERE time > '2021-12-31 00:00:00+00'::timestamptz | ||||||
ORDER BY time ASC | ||||||
FROM metrics m2 | ||||||
WHERE time < '2021-12-31 00:00:00+00'::timestamptz AND | ||||||
m.device_id=m2.device_id | ||||||
ORDER BY time DESC | ||||||
LIMIT 1 | ||||||
), | ||||||
( | ||||||
SELECT (time, value) | ||||||
FROM metrics | ||||||
WHERE time < '2021-12-10 00:00:00-00'::timestamptz | ||||||
ORDER BY time DESC | ||||||
FROM metrics m2 | ||||||
WHERE time > '2021-12-10 00:00:00-00'::timestamptz AND | ||||||
m.device_id=m2.device_id | ||||||
ORDER BY time ASC | ||||||
LIMIT 1 | ||||||
) | ||||||
) as value | ||||||
FROM metrics | ||||||
FROM metrics m | ||||||
WHERE time > '2021-12-31 00:00:00+00'::timestamptz | ||||||
AND time < '2022-01-10 00:00:00-00'::timestamptz | ||||||
GROUP BY day | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add this to the
group by
clause too?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes good point.
GROUP BY device_id, day
.device_id should be either in GROUP BY or WHERE to make query realistic.