Bug: charts are not timezone-aware

[mindreframer]

I have noticed by playing with the data after 22h Berlin time (UTC +2), that some impressions are missing. When switching to tomorrow, I could see them again.

Maybe it should be possible to somehow respect the timezone? Not sure, how much more complex the DB schema will get, but it was actually somewhat confusing to not be be able to see the the recent impressions in the dashboard. I thought this is somehow related to caching, an maybe it also was. Before 22h I had to restart the phoenix server to get the most recent entries from the requests tables to be shown in the dashboard.

2 possible options I could imagine:

• expire the cache after new impressions (so-so perfmance-wise)
• give the user the ability to re-fresh the stats per widget and maybe have an indicator of the timestamp, then the cache was created. That way the user can always decide if he/she wants to get the most up-to-date info or keep some-what stale values.

[lalabuy948]

Hi @mindreframer ,

Indeed data is cached and if you switch from default date range to today/tomorrow/(any new one) you will see new requests. Where on page refresh you might not see same behavior as previous values where cached.

In that regard, in the upcoming version I will disable it by default and make configurable via config/config.exs. You can take a look on this PR description.

Let me know if that PR going to fix your concerns.

p.s. Since, I accept the fact it was a bit of over-engineering from my side, as I already introduced separate read only connection cache seems a bit over kill. In new version will fix it.