You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect that has been designed for PostgreSQL and does not work with sqlite. Apparently, that only works in MySQL (and PostgreSQL i guess?)... the sqlite-way of doing this seems to be, according to SO:
SELECT mumble FROM blah WHERE blah.heart_beat_time > datetime('now', '-600 seconds');
... and obviously, that is a SQLite-specific extension that doesn't work in the other two...whee!
The text was updated successfully, but these errors were encountered:
I just created this quickly after an outage several months ago to make sure I would be notified ASAP, kinda forgot about SQLite 😅 There's already a little helper to deal with this specific syntax difference. Should be a simple fix.
I get this when running
goatcounter monitor:I figured maybe something was up with defaults, so I also tried overriding the
-period:(Note that I use Docker, above, but that should be equivalent to just running
goatcounter monitor -period 120.)The errors comes back once in a while, about every two minutes...
It seems like this is a problem with this database query:
I suspect that has been designed for PostgreSQL and does not work with sqlite. Apparently, that only works in MySQL (and PostgreSQL i guess?)... the sqlite-way of doing this seems to be, according to SO:
... and obviously, that is a SQLite-specific extension that doesn't work in the other two...whee!
The text was updated successfully, but these errors were encountered: