Elad Meidar

Close this ticket, tried several urls and they all pass.

attached a test to check this specific example, it passes on 2-3-stable

@Peter: mmm, do you see anywhere else it needs to be applied except for a foreign key assignment in a :belongs_to association?

Bryan, can you supply a patch within a single file? please ? :)

+1 verified. not sure that this is the right solution thu, maybe there's a way to scope the metal models under Metal:: ?

Mmmm,
by doing

- self.attributes = attributes unless attributes.nil?
  self.class.send(:scope, :create).each { |att,value| self.send("#{att}=", value) } if se...

Mmmm,
by doing

-        self.attributes = attributes unless attributes.nil?

     self.class.send(:scope, :create).each { |att,value| self.send("#{at...

+1 verified on 2-3-stable, i tried to follow up named_scope.rb and try to point to where exactly the :include option is dropped/ignored when set within a lambda...

+1 verified

if join_table is missing from the macro options, the join table name will be calculated on associations.rb#1596, by using undecorated_table_name (ht...

-1 current situation is expected and concurrent with other attribute behaviors. The reason for that is that there is no actual save upon the new association id ...