Default Scope with conditions on create

I noticed the same thing and it made me uneasy.

class Event < ActiveRecord::Base
  default_scope :conditions => "id = 1"
end

Event.new

NoMethodError: undefined method `id = 1=' for #<Event:0xb6dc2cf4>
	from /home/david/Sites/azurrofashion.com/azurrofashion/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:255:in `method_missing'
	from /home/david/Sites/azurrofashion.com/azurrofashion/vendor/rails/activerecord/lib/active_record/base.rb:2440:in `send'
	from /home/david/Sites/azurrofashion.com/azurrofashion/vendor/rails/activerecord/lib/active_record/base.rb:2440:in `initialize'
	from /home/david/Sites/azurrofashion.com/azurrofashion/vendor/rails/activerecord/lib/active_record/base.rb:2440:in `each'
	from /home/david/Sites/azurrofashion.com/azurrofashion/vendor/rails/activerecord/lib/active_record/base.rb:2440:in `initialize'
	from (irb):3:in `new'
	from (irb):3

Is this the same issue?

Default_scopes do not currently behave the same as named_scopes which is weird. I've added a patch that helps to improve consistency. It may be able to help with your problem. http://rails.lighthouseapp.com/p...

Regarding the example posted by David, this is happening because default_scope should be checking whether :conditions is a hash. Instead it is checking whether options is a hash, as well as merely checking whether :conditions exists. The check on options seems pointless as it would always be a hash, right?

I came up with the following patch but it got me wondering what named_scope does about this. It turns out named_scope.rb does exactly the same thing as my patch! I'm not sure why default_scope was done any differently.

Sorry, the test wasn't quite right. Wasn't thinking straight.

(from [c5e109bbe766b0407a909361f18d2b87e9bfc75c]) Make sure default_scope#create checks for options[:conditions] [#2181 Default Scope with conditions on create state:resolved] [James Le Cuirot] http://github.com/rails/rails/commit/c5e109bbe766b0407a909361f18d2b...