Eloy Duran

Jeez, formatting is a pita. I edited it a few times, hope you can understand it.

However, if I do something like this:

@@@ ruby a = ModelA.create a.model_bs << ModelB.create a.valid? # => true a.model_bs.first.name = nil a.valid? # => true ...

It would be very helpful if you could identify where (if) this was introduced.

Thanks

Indeed, as José spotted correctly, when explicitly setting :validate => true on the belongs_to :parrot association it works as you expected it to:

  1) Error...

Just by curiosity, even with :validate => true this happens? If I'm not mistaken, :validate => false is the default in belongs_to associations.

That's correct...

The documentation (meaning comments in autosave_association.rb) seems to imply that :autosave is a feature you have to turn on by enabling :autosave => true on...

Could you please try to distill a failing test for the exact problem you are having? That would be greatly appreciated.

Thanks

Callbacks aren't ran, cause we use only record.destroy. Code similar to this is in AssociationProxy#delete, but it run also unwanted callbacks.

Oh, I actually...

Just to clarify a bit. Judging by the tag you are sure this was introduced in the first 2.3 release candidate?

• if :autosave were true on Pirate belongs_to :parrot then the pirate save should have failed with a validation error

I agree

• if :autosave were false on Pir...