ffeb70f787
It only served for a niche, admin nice-to-have informational stat without too much value but was unreasonably costly to maintain adding overhead with multiple queries added to all modifications to the fairly busy activities table. The database schema of the counter table and the activity_visibility function used for counter updates also did not know about "local" visibility (nor the recently removed "list" visibility) and misattributed them to the "direct" counter. On my small instance this nearly halved the average insert time for activiteis from 0.926 ms to 0.465 ms. |
||
|---|---|---|
| .. | ||
| controllers | ||
| views | ||
| report.ex | ||
| search.ex | ||