Skip to content
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

Typo fixups (Matching with Materialize.com blog) #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Typo fixups (Matching with Materialize.com blog) #48

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
6 changes: 3 additions & 3 deletions posts/2020-12-29.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,7 @@ Expressing a request for a week-long interval would require 10,080 minutes as in

However, no one said you had to use only minutes. Or only hours.
You can cover most of your hypothetical week with daily aggregates, six at least.
You can then just grab a few houly aggregates at each end, and a few minutely aggregates if you want those too.
You can then just grab a few hourly aggregates at each end, and a few minutely aggregates if you want those too.

Let's spell this out with an example, as it will be important to be clear.
Let's say your request times are
Expand Down Expand Up @@ -239,7 +239,7 @@ We'll write some queries in the appendix that automatically produce these interv

---

For now, let's imagine for now we have your request input in this more expansive representation.
For now, let's imagine we have your request input in this more expansive representation.
How might you get your aggregate results out?
What SQL queries do we need to write to make that happen?

Expand Down Expand Up @@ -498,4 +498,4 @@ WHERE
GROUP BY
key,
passenger_count;
```
```