binding_of_caller and scope instance variables

[elDub]

When the better_errors page is displayed with the binding_of_caller gem enabled, any ActiveRecord scopes are inspected/expanded, which can result in entire database tables being loaded and inspected. Is it possible, or even acceptable in this situation, to perhaps not inspect the scope but rather '.to_sql' it? Maybe make that an option? Or perhaps this is more of an issue for the binding_of_caller gem?

For example, if the companies table has thousands of active records, the following will trigger a very large amount of output:

class CompaniesController < ApplicationController
  before_filter :set_resource_scope

  def index
    @resource_scope = @resource_scope.order(Company.arel_table[:name].asc)
    raise Exception
  end

  private

  def set_resource_scope
    @resource_scope = Company.active
  end
end

[cknoxrun]

+1, I'm having this issue as well.

[findchris]

Any idea why this is happening?

[haileys]

This happens because the inspect method on ActiveRecord::Relation actually performs the query and inspects the result data. I believe Rails 4 changes this behaviour so inspect doesn't dump such a massive amount of data.

[haileys]

This is fixed in Rails 4