Flush history, delete from database

[mplx]

Under "History" you can "flush (the) history" of all feeds, where technically all "read" articles are marked as "removed".

1. I subscribed some feeds which are getting quite a lot of entries so I was looking for some method to mark read articles as removed from a specific feed to early get rid of them while keeping default CLEANUP_* settings for others. Maybe this would be useful to others too so I thought about an feature request - on the feeds page: would you add a "flush history" entry next to the other feed specific operations (refresh, edit, remove, mark as read) which will just operate on entries of this single feed?

2. I wondered how often these removed articles get physically deleted from the database? I found the function cleanupEntries which seems to just exactly do this however I did not find where or how often it gets called. (btw, I'm using the official docker container).

PS: Thank you very much for creating miniflux - it's fantastic! :)

[shizunge]

The cleanupEntries is called in RefreshFeedEntries isn't?

The schedule is setup in https://github.com/miniflux/v2/blob/master/service/scheduler/scheduler.go

[fguillot]

Default values for cleanup actions are documented here as well: https://miniflux.app/docs/configuration.html#cleanup-frequency-hours

[mplx]

Thank your for your replies.

What I was trying to achive is to clean specific feeds in other intervals than defined in mentioned CLEANUP_* entries (which are perfectly documented, however the docs refer to when an entry gets marked as removed, not when it gets deleted), thus I was looking in the source code to see how I can properly set entries as removed.

I came up with a statement like UPDATE entries SET status='removed' WHERE feed_id=XXX AND changed_at <= (NOW() - INTERVAL '48 hours') to set an earlier expiration time for entries of a specific feed

When searching when and how miniflux deletes the records physically I found the above mentioned cleanupEntries which seems to be the only DELETE FROM entries in the full sourcecode.

Wondering if a statement like DELETE FROM entries WHERE feed_id=XXX AND changed_at <= (NOW() - INTERVAL '48 hours') would be better solution I tried to find out when this is exectued (meanwhile I found the chain RefreshFeedEntries < RefreshFeed < WorkerRun).

At the end of the day, a cron script calling sql statements isn't very satisfying nor reliable, thus I came up with the feature request to have a "flush history" for each feed in the feeds view like the "flush history" in the history view for all feeds.

[shizunge]

I have created a bug #770 for per feed retention policy
I hope @fguillot can review and merge #949 firstly, before I start working on #770.