Re: [Rails] Re: Why doesn't collection=objects on has_many :through trigger destroy callbacks on the join model?

Just reporting back, it works as expected on my end too. Thanks for the feedback. This solution feels more proper :) Linking in the PR for the documentation change for others finding this thread in the future: https://github.com/rails/rails/pull/22644 Cheers, Brendon On Friday, December 18,

[Rails] Re: Why doesn't collection=objects on has_many :through trigger destroy callbacks on the join model?

I responded on stackoverflow, but I'll do here as well so that it is covered everywhere on the internet. In my case I was doing something similar to what you were doing and was running into the same issue with the join table being deleted instead of destroyed. I started looking through the

Re: [Rails] Re: Why doesn't collection=objects on has_many :through trigger destroy callbacks on the join model?

I just did that this morning. On Thursday, December 17, 2015, spike22 wrote: > Hi Eric, that's really interesting! I'll give it a whirl and report back > :) I might do a documentation pull request to clarify this too. > > Have a great day! > > Brendon > > On Friday,

[Rails] Re: Why doesn't collection=objects on has_many :through trigger destroy callbacks on the join model?

Hi Eric, that's really interesting! I'll give it a whirl and report back :) I might do a documentation pull request to clarify this too. Have a great day! Brendon On Friday, December 18, 2015 at 6:23:50 AM UTC+13, Eric Krause wrote: > > I responded on stackoverflow, but I'll do here as well so

Re: [Rails] Re: Why doesn't collection=objects on has_many :through trigger destroy callbacks on the join model?

Haha! very good :) On Friday, December 18, 2015 at 10:39:49 AM UTC+13, Eric Krause wrote: > > I just did that this morning. > > On Thursday, December 17, 2015, spike22 > wrote: > >> Hi Eric, that's really interesting! I'll give it a whirl and report back >> :) I