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
Maybe run VACUUM when aw-server is starting up?
Seems like a sane time to do it.
If the operation is somewhat costly then I'd rather not as that could slow down the startup time of the Android app (less of a concern on desktop, where the user is unlikely to use ActivityWatch the moment it's started).
If the operation is somewhat costly then I'd rather not as that could slow down the startup time of the Android app (less of a concern on desktop, where the user is unlikely to use ActivityWatch the moment it's started).
Hm, I guess that's true.
A solution would be to have it as both an API endpoint to manually start a VACUUM as well as maybe store the last time a VACUUM was performed and do it once every X months.
So the delete endpoint for a single event just as for aw-server-python is now implemented but there is no VACUUM for now.
Maybe we should have a new issue for VACUUM?
Activity
[-]DELETE endpoint to delete event[/-][+]DELETE endpoint to delete event(s)[/+]ErikBjare commentedon Aug 28, 2019
We should keep in mind that we might want to use the pragma
secure_deleteor run aVACUUMto ensure secure deletion of data.johan-bjareholt commentedon Aug 28, 2019
Maybe run VACUUM when aw-server is starting up?
Seems like a sane time to do it.
johan-bjareholt commentedon Aug 28, 2019
secure_delete=FAST seems like the best approach for us I believe.
ErikBjare commentedon Aug 28, 2019
If the operation is somewhat costly then I'd rather not as that could slow down the startup time of the Android app (less of a concern on desktop, where the user is unlikely to use ActivityWatch the moment it's started).
johan-bjareholt commentedon Aug 28, 2019
Hm, I guess that's true.
A solution would be to have it as both an API endpoint to manually start a VACUUM as well as maybe store the last time a VACUUM was performed and do it once every X months.
johan-bjareholt commentedon Jan 14, 2020
So the delete endpoint for a single event just as for aw-server-python is now implemented but there is no VACUUM for now.
Maybe we should have a new issue for VACUUM?
johan-bjareholt commentedon Apr 5, 2020
Updated the issue body
feat(server): bulk event delete endpoint POST /buckets/<id>/events/de…