1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-25 13:19:37 -05:00
forgejo/tests/integration/fixtures
Gusted 3d3790ef4c
[MODERATION] Refactor excluding watchers mechanism (squash)
Backport of #2143

This solves two bugs. One bug is that due to the JOIN with the
`forgejo_blocked_users` table, duplicated users were generated if a user
had more than one user blocked, this lead to receiving more than one
entry in the actions table. The other bug is that if a user blocked more
than one user, it would still receive a action entry by a
blocked user, because the SQL query would not exclude the other
duplicated users that was generated by the JOIN.

The new solution is somewhat non-optimal in my eyes, but it's better
than rewriting the query to become a potential perfomance blocker (usage
of WHERE IN, which cannot be rewritten to a JOIN). It simply removes the
watchers after it was retrieved by the SQL query.

(cherry picked from commit c63c00b39b)
2024-01-22 21:01:08 +01:00
..
TestAdminDeleteUser [MODERATION] User blocking 2023-11-13 13:58:02 +01:00
TestBlockActions [MODERATION] User blocking (squash) do not use shared fixture 2023-11-26 13:56:00 +01:00
TestBlockedNotifications [MODERATION] Refactor excluding watchers mechanism (squash) 2024-01-22 21:01:08 +01:00
TestGetContentHistory [GITEA] Fix panic in canSoftDeleteContentHistory 2024-01-13 22:05:35 +01:00