DISTINCT clause removes duplicated records according to all the selected attributes. In reality, it can remove duplicated records only looking at statuses.id, but the clause confuses the query planner and yields insufficient performance. The behavior is also problematic if the scope produced by HashQueryService is used to query columns without id (using pluck method, for example). The scope is expected to contain unique statuses, but the uniquness will be evaluated with some arbitrary columns other than id. GROUP BY clause resolves those problem by explicitly specifying the column to take into account for the record distinction. A workaround for the problem of DISTINCT clause in Api::V1::Timelines::TagController is no longer necessary and removed.
22 lines
549 B
Ruby
22 lines
549 B
Ruby
# frozen_string_literal: true
|
|
|
|
class HashtagQueryService < BaseService
|
|
LIMIT_PER_MODE = 4
|
|
|
|
def call(tag, params, account = nil, local = false)
|
|
tags = tags_for(Array(tag.name) | Array(params[:any])).pluck(:id)
|
|
all = tags_for(params[:all])
|
|
none = tags_for(params[:none])
|
|
|
|
Status.group(:id)
|
|
.as_tag_timeline(tags, account, local)
|
|
.tagged_with_all(all)
|
|
.tagged_with_none(none)
|
|
end
|
|
|
|
private
|
|
|
|
def tags_for(names)
|
|
Tag.matching_name(Array(names).take(LIMIT_PER_MODE)) if names.present?
|
|
end
|
|
end
|