Rails 4 ActiveRecord includes(:model) without its default_scope

Question

I have the following situation in my Rails app. There are two models, let's say User and Company:

class User < ActiveRecord::Base
  belongs_to :company
  default_scope -> {where(removed_at: nil)}
end

and

class Company < ActiveRecord::Base
  has_many :users
end

What I want now is loading an Company record and include the Users

Company.unscoped.all.includes(:users)

What will result in a query to the users table which includes the default-scope. So I get the Company record with all not removed users prefetched. But in this case I do also want the Users where removed_at is not null (=> the removed User records). The "unscoped" method is only applied to the Company model, not to the User model.

Is there any way to do this? Thanks for any ideas!

score 4 · Answer 1 · answered Jul 24 '14 at 16:16

Here is the solution I got working in my Rails 4.0 application

class User < ActiveRecord::Base
  belongs_to :company
  default_scope -> {where(removed_at: nil)}
end

class UserUnscoped < User
  self.default_scopes = []
end

class Company < ActiveRecord::Base
  has_many :users, class_name: "UserUnscoped"
end

Company.unscoped.all.includes(:users)

user2503775 · Answer 2 · 2013-10-10T10:59:19.330

3

This method accepts a block. All queries inside the block will not use the default_scope:

User.unscoped { Company.includes(:users).all }

or:

User.unscoped do
 Company.includes(:users).all
end

edited Oct 10 '13 at 10:59

answered Oct 10 '13 at 10:12

user2503775

4,267
1
23
41

4

Nope, unfortunately this doesn't avoid calling the default_scope (Rails 4). – milkman Oct 10 '13 at 10:37
Try removing the `all` to the end. – user2503775 Oct 10 '13 at 10:48
1

Both versions are not working for me, neither with nor without the (deprecated) all. – milkman Oct 10 '13 at 12:57
In Rails 3 it sure works . http://stackoverflow.com/a/14446317. Maybe there is a problem in Rails 4 – user2503775 Oct 10 '13 at 13:15
You must the `all` to execute the query into the block. I mean you should pass it to the end. – user2503775 Oct 10 '13 at 13:23
Thanks for pointing on the other thread. Is anyone able to reproduce this under Rails 4 ? – milkman Oct 10 '13 at 14:38

score 2 · Answer 3 · answered Mar 23 '21 at 15:37

The relation is not preserving this state, when accessing it later (Rails 6.0)

A possible workaround for some cases is forcing the resolution, e.g.:

User.unscoped { Company.includes(:users).to_a }

to_a resolves the relation while in the block, so the scope is effectively removed.

score 0 · Answer 4 · answered Nov 26 '15 at 17:00

I had a greatly-branched STI models set. So the only approach, which works for me (Rails 4.2.5) is the following:

class UndeadUser < ActiveRecord::Base
  self.table_name = 'users'
end

class User < UndeadUser
  # real logic here
end

class Employee < User; end
class Manager < Employee; end

# grouping model
class Organization < ActiveRecord::Base
  has_many :employees

  has_many :users, class: UndeadUsers
  before_destroy :really_destroy_users_and_data! # in case of using acts_as_paranoid or paranoia gems it might be helpful
end

Solution from @abstractcoder doesn't work for me, because rails try to add WHERE users.type IN ('UndeadUser') when UndeadUser inherited from User.

Rails 4 ActiveRecord includes(:model) without its default_scope

4 Answers4