forgejo/models/fixtures/action.yml
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

86 lines
1.4 KiB
YAML

-
id: 1
user_id: 2
op_type: 12 # close issue
act_user_id: 2
repo_id: 2 # private
is_private: true
created_unix: 1603228283
-
id: 2
user_id: 3
op_type: 2 # rename repo
act_user_id: 2
repo_id: 3 # private
is_private: true
content: oldRepoName
-
id: 3
user_id: 11
op_type: 1 # create repo
act_user_id: 11
repo_id: 9 # public
is_private: false
-
id: 4
user_id: 16
op_type: 12 # close issue
act_user_id: 16
repo_id: 22 # private
is_private: true
created_unix: 1603267920
- id: 5
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 6 # private
is_private: true
created_unix: 1603010100
- id: 6
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 7 # private
is_private: true
created_unix: 1603011300
- id: 7
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 8 # public
is_private: false
created_unix: 1603011540 # grouped with id:7
- id: 8
user_id: 1
op_type: 12 # close issue
act_user_id: 1
repo_id: 1700 # dangling intentional
is_private: false
created_unix: 1603011541
- id: 9
user_id: 34
op_type: 12 # close issue
act_user_id: 34
repo_id: 1 # public
is_private: false
created_unix: 1680454039
content: '4|' # issueId 5
- id: 10
user_id: 15
op_type: 10 # issue comment
act_user_id: 15
repo_id: 32 # public
comment_id: 8
is_private: false
created_unix: 1680454039
content: '2|meh...' # issueId 5