I highly value your work on the rails framework.
I recently upgraded rails fro 2.3.5 to 2.3.8, and my tests revealed a
problem.
I switch to git 2-3-stable branch and used git bisect to isolate the
first bad commit, and it showed to be
5efb1503dd88b59fe491dade92790c3f06293445
The problem is that using {:_destroy => "1"} on a nested (has_many)
model has no effect after the bad commit.
Can someone please help me write a minimal test (along the other AR
tests) for illustrating the problem and to prevent this from happen
again in the future.
Jarl
We have temporarily worked around it by forcing the association to load before setting the attributes.
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To unsubscribe from this group, send email to rubyonrails-co...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
>
--
Luke Melia
http://www.lukemelia.com/
I've added a ticket with failing tests and a summary of the problem. I'm happy to prepare a patch with a "fix" if I can get some guidance on what the expected behavior ought to be here.
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4766
Cheers,
Luke
Cheers,
Lawrence