“where”覆盖了我在 rails 中的默认“order”

问：

我正在尝试根据结果制作一个 qyery，我正在为某些任务应用另一个查询。

在这里，我有一种filter_based_on_ticket_creation方法，其中我根据降序获取一些数据，这是我的过滤器之一，基于该数据，我正在进行另一个查询，这将提供一些我想要显示的其他详细信息。

这是最狡猾的，

  def fetch_deallocations_based_on_department
    department = params[:department]
    deallocations = []
    filter_based_on_ticket_creation(params).joins(:resource_info).where('resource_infos.department_name = ?',department).order(due_date: :asc).limit(5).each do |details|
      deallocations.push([details.developer.name,details.due_date.present? ? details.due_date&.strftime('%d / %m / %Y') : 'Date not assigned'])
    end
    render json: deallocations
  end


  def filter_based_on_ticket_creation(params)
    if (params[:q].present? && params[:q][:updated_at_lteq].present?)
      @q.result.order(updated_at: :desc).limit(params[:q][:updated_at_lteq].to_i)
    else
      @q.result
    end
  end

在这里我总共有 32 条撤派记录，

irb(main):002:0> Deallocation.all.pluck(:id)
  Deallocation Pluck (0.5ms)  SELECT "deallocations"."id" FROM "deallocations"
=> [75, 24, 25, 26, 82, 27, 28, 74, 36, 41, 78, 58, 76, 53, 29, 40, 81, 30, 77, 23, 38, 39, 54, 68, 57, 70, 71, 72, 79, 73, 80, 83]

所以现在我想做一个过滤器，给出最新的 5 或 10 张票，为此我做了一种方法（filter_based_on_ticket_creation（params））给我最新的数据，基于updated_at意味着它给出最新的 5 条记录或 10 条记录 这里filter_based_on_ticket_creation（params）返回一些数据

  Deallocation Load (0.4ms)  SELECT "deallocations".* FROM "deallocations" ORDER BY "deallocations"."updated_at" DESC LIMIT $1 
pry(#<DeallocationsController>)> @filterd_deallocation.pluck(:id)
=> [75, 83, 82, 81, 40]

因此，在应用此过滤器后，我有 2 个用例，一个是我想显示这 5 条记录，另一个用例是我在过滤后的数据上应用一些 where 和 join 条件。

当我在我的 fetch_deallocations_based_on_department 方法上应用 where 条件时，它将覆盖查询并给出不同的输出

 @filterd_deallocation.joins(:resource_info).where('resource_infos.department_name = ?','ROR')
  Deallocation Load (0.6ms)  SELECT "deallocations".* FROM "deallocations" INNER JOIN "cims"."resource_infos" ON "cims"."resource_infos"."id" = "deallocations"."resource_info_id" WHERE (resource_infos.department_name = 'ROR') ORDER BY "deallocations"."updated_at" DESC LIMIT $1  [["LIMIT", 5]]

@filterd_deallocation.joins(:resource_info).where('resource_infos.department_name = ?','ROR').pluck(:id)
  Deallocation Pluck (1.3ms)  SELECT "deallocations"."id" FROM "deallocations" INNER JOIN "cims"."resource_infos" ON "cims"."resource_infos"."id" = "deallocations"."resource_info_id" WHERE (resource_infos.department_name = 'ROR') ORDER BY "deallocations"."updated_at" DESC LIMIT $1  [["LIMIT", 5]]
  ↳ (pry):4:in `deallocation_dashboard'
=> [75, 83, 40, 29, 53] # here additional 40,29,53 ids are coming

所以在这里你可以看到 在 SQL 中，filter_based_on_ticket_params方法进行此查询

ELECT "deallocations".* FROM "deallocations" ORDER BY "deallocations"."updated_at" DESC LIMIT $1 

所以当我应用这个查询时

filter_based_on_ticket_creation(params).joins(:resource_info).where('resource_infos.department_name = ?',department).order(due_date: :asc).limit(5) 

它将覆盖默认查询，因为 SQL 查询的执行顺序，其中“where”的优先级高于“order”，因此它将首先进行“where”查询，并基于该数据进行“order”

SELECT "deallocations".* FROM "deallocations" INNER JOIN "cims"."resource_infos" ON "cims"."resource_infos"."id" = "deallocations"."resource_info_id" WHERE (resource_infos.department_name = 'ROR') ORDER BY "deallocations"."updated_at" DESC LIMIT $1 

所以我想要一个持久查询，我该怎么办意味着第二个查询不会改变SQL流的执行，我只根据我的第一个查询数据得到结果。