I find that many places need a spine.
You probably refer to one of the demos on our landing page?
I like how you describe the problem. You're absolutely right that SQL seems easy but it's these edge cases that make it hard to get right. Joining metrics with a date spine is definitely a good practice to avoid missing date periods.
I think we could/should teach Dot to do that in the future. It should at least be a feature you can turn on as the data team.
Indeed, not sure how I ended up there but did on mobile, commented here.
> You're absolutely right that SQL seems easy but it's these edge cases that make it hard to get right
SQL/data analysis is endlessly pesky! I assume it would be easier to spot on tighter increments like "minutely" or "hourly"
> It should at least be a feature you can turn on as the data team.
Some might want the missing points, others wont - sounds like a good option (but id default to "enabled", each to their own though)
Having a date dimension provides an elegant solution in many cases.
Also once you start saying "i want secondly/minutely breakdowns", the dimension (neat term) gets pretty...large (probably less than the TB of data though)
It asks ChatGPT to write SQL to get sales data, ChatGPT (or most SQLers) trust that every year-month combo has atleast one entry - which means the graphs its presenting could be wrong. Because if there was no entries for a year-month it it will skip that year-month and make it look like you never had a 0 month.
I've made this mistake before in prod, and without some janky lookup table of every date in existence... you need more code :( Fairly few people actually notice the potentially missing month, but still its a bug n a bad one.
Looks cool regardless though, good luck!