Closed ZacharyDuBois closed 1 year ago
Updated my issue title and body after I got some caffeine to realize it was an entirely simpler issue. Like above, I will submit a PR over the weekend, thanks for this library!
@ZacharyDuBois have you had time to work on the PR?
Closing stale issue
Apparently my original assumption was entirely incorrect. This is an issue specifically with the
PgsqlAdapter
specifically line 13 for the hourly aggregate. You have seconds included when it should only be scoped to the hours hence the duplication issue when you pad the returned aggregate for missing intervals. I have made an override class for my project. I will create a PR this weekend :)Original thought below (with lack of caffeine): Hi,
When using
Trend
to get aggregate data using a date column that contains milliseconds in pgsql, it will returnTrendValue
s with and without seconds for the same interval. See example code and output below.Migration:
Model:
Trend call:
Output:
Look at the pointers 5434 and 5395, they are for the same interval but one was returned with seconds. This happens for every period where data exists. So all the periods with no data, it does not happen.