Mongoid default scope overrides default value. Why?

Question

mongoid 4.0.2

I have Test class:

class Test
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::Paranoia

  field :successful,      type: Boolean, default: false

  default_scope  ->{ where(successful: true) }
end

Then I do:

t=Test.new; t.successful
=> true

So here is the question: what is the reason behind this behaviour?

P.S. I have fixed it resetting successful with the help of after_initialize method.

This sounds like a bug. Have you confirmed it is the `default_scope` that's causing this? — Drenmi, Oct 07 '15 at 14:30
@Drenmi When I remove line with default_scope everything is ok, so I guess yeah. — Maxim Pontyushenko, Oct 07 '15 at 14:48

score 1 · Answer 1 · edited May 23 '17 at 12:15

Try calling Test.create(), successful will also be true. This seems strange, but think what you are saying in your default_scope... get all tests that are true.

This looks like something that came from active_record originally: rails3 default_scope, and default column value in migration however it is strictly followed active_record this should work, however it doesn't:

t= Test.unscoped.new; t.successful
=> true

In the mongo world, if you put on a default_scope it'll scope all objects with that and assume that you would want anything new to also have that same default. The work arounds are using callbacks. You mentioned hooking up the after_initialize which is a good choice, however you need to make sure you check whether it has actually been set. Another alternative would be to use a named scope rather than the default.

Mongoid default scope overrides default value. Why?

1 Answers1