forgejo/models/activities
Gusted 9b71369be9 [GITEA] Use join for the deleting issue actions query
- The action tables can become very large as it's a dumpster for every
action that an user does on an repository.
- The following query: `DELETE FROM action WHERE comment_id IN (SELECT id FROM comment WHERE
issue_id=?)` is not using indexes for `comment_id` and is instead using
an full table scan by MariaDB.
- Rewriting the query to use an JOIN will allow MariaDB to use the
index.
- More information: https://codeberg.org/Codeberg-Infrastructure/techstack-support/issues/9
- Backport https://codeberg.org/forgejo/forgejo/pulls/1154
2023-07-31 10:14:30 +00:00
..
action.go [GITEA] Use join for the deleting issue actions query 2023-07-31 10:14:30 +00:00
action_list.go
action_test.go [GITEA] Use join for the deleting issue actions query 2023-07-31 10:14:30 +00:00
main_test.go
notification.go [MODERATION] user blocking 2023-07-17 00:26:42 +02:00
notification_test.go
repo_activity.go Add context cache as a request level cache (#22294) 2023-02-15 21:37:34 +08:00
statistic.go Use a separate admin page to show global stats, remove actions stat (#25062) 2023-06-03 22:03:41 +08:00
user_heatmap.go Localize activity heatmap (except tooltip) (#24131) 2023-04-17 14:26:01 -04:00
user_heatmap_test.go Add pagination for dashboard and user activity feeds (#22937) 2023-02-24 16:15:10 -05:00