Why is using the rails default_scope often recommend against?

by

Problem 1

Lets consider the basic example: 

class Post < ActiveRecord::Base
  default_scope { where(published: true) }
end

The motivation to make the default published: true, might be to make sure you have to be explict when wanting to show unpublished (private) posts. So far so good.

2.1.1 :001 > Post.all
  Post Load (0.2ms)  SELECT "posts".* FROM "posts"  WHERE "posts"."published" = 't'

Well this is pretty much what we expect. Now lets try: 

2.1.1 :004 > Post.new
 => #<Post id: nil, title: nil, published: true, created_at: nil, updated_at: nil>

And there we have the first big problem with default scope:

=> default_scope will affect your model initialization

In a newly created instance of such a model, the default_scope will be reflected. So while you might have wanted to be sure to not list unpublished posts by chance, you’re now creating published ones by default.

Problem 2

Consider a more elaborate example: 

class Post < ActiveRecord::Base
  default_scope { where(published: true) }
  belongs_to :user
end 

class User < ActiveRecord::Base
  has_many :posts
end

Lets get the first users posts: 

2.1.1 :001 > User.first.posts
  Post Load (0.3ms)  SELECT "posts".* FROM "posts"  WHERE "posts"."published" = 't' AND "posts"."user_id" = ?  [["user_id", 1]]

This looks like expected (make sure to scroll all the way to the right to see the part about the user_id).

Now we want to get the list of all posts – unpublished included – say for the logged in user’s view. You’ll realise you have to ‘overwrite’ or ‘undo’ the effect of default_scope. After a quick google, you’ll likely find out about unscoped. See what happens next: 

2.1.1 :002 > User.first.posts.unscoped
  Post Load (0.2ms)  SELECT "posts".* FROM "posts"

=> Unscoped removes ALL scopes that might normally apply to your select, including (but not limited to) associations.

There are multiple ways to overwrite the different effects of the default_scope. Getting that right gets complicated very quickly and I would argue not using the default_scope in the first place, would be a safer choice.

More Related Contents:

  1. Single table inheritance and where to use it in Rails
  2. Is there a way to get a collection of all the Models in your Rails app?
  3. No route matches “/users/sign_out” devise rails 3
  4. difference between collection route and member route in ruby on rails?
  5. Disable ActiveRecord for Rails 4
  6. Creating a many to many relationship in Rails
  7. Rails model without database
  8. Paperclip exception : Paperclip::AdapterRegistry::NoHandlerError
  9. Using Rails serialize to save hash to database
  10. Rails 3: Get Random Record
  11. Setting session timeout in Rails 3
  12. Rails 4 link_to Destroy not working in Getting Started tutorial
  13. rails 3.1.0 ActionView::Template::Error (application.css isn’t precompiled)
  14. Adding lib to ‘config.autoload_paths’ in Rails 3 does not autoload my module
  15. Rails 4 image-path, image-url and asset-url no longer work in SCSS files
  16. How do I set up email confirmation with Devise?
  17. Named routes _path vs _url
  18. How to sign in a user using Devise from a Rails console?
  19. Using Rails-UJS in JS modules (Rails 6 with webpacker)
  20. Check if record exists from controller in Rails
  21. How to get request referer path?
  22. Extending controllers of a Rails 3 Engine in the main app
  23. Difference between Render and Render Partial and Yield
  24. How to implement Active Record inheritance in Ruby on Rails?
  25. Setup sunspot solr with rails in production environment
  26. Ruby on rails 4 app does not work in iframe
  27. Are redirect_to and render exchangeable?
  28. Rails 3 invalid multibyte char (US-ASCII)
  29. How do I remove lines of data in the middle of a text file with Ruby
  30. Rails: Order with nulls last

Leave a Comment