Fix response_to_recipient? CTE (#17427)

rebase/4.0.0rc2
Claire 2022-02-03 14:07:43 +01:00 committed by GitHub
parent d1ecc323e7
commit 948235592a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions

View File

@ -73,9 +73,11 @@ class NotifyService < BaseService
# Using an SQL CTE to avoid unneeded back-and-forth with SQL server in case of long threads
!Status.count_by_sql([<<-SQL.squish, id: @notification.target_status.in_reply_to_id, recipient_id: @recipient.id, sender_id: @notification.from_account.id]).zero?
WITH RECURSIVE ancestors(id, in_reply_to_id, replying_to_sender) AS (
WITH RECURSIVE ancestors(id, in_reply_to_id, replying_to_sender, path) AS (
SELECT
s.id, s.in_reply_to_id, (CASE
s.id,
s.in_reply_to_id,
(CASE
WHEN s.account_id = :recipient_id THEN
EXISTS (
SELECT *
@ -84,7 +86,8 @@ class NotifyService < BaseService
)
ELSE
FALSE
END)
END),
ARRAY[s.id]
FROM statuses s
WHERE s.id = :id
UNION ALL
@ -100,10 +103,11 @@ class NotifyService < BaseService
)
ELSE
FALSE
END)
END),
st.path || s.id
FROM ancestors st
JOIN statuses s ON s.id = st.in_reply_to_id
WHERE st.replying_to_sender IS FALSE
WHERE st.replying_to_sender IS FALSE AND NOT s.id = ANY(path)
)
SELECT COUNT(*)
FROM ancestors st