On Mar 23, 2:19 pm, djangst <[email protected]> wrote: > After upgrading 3.0.4 -> 3.0.5 one of my tests now fails on an > assertion like 'assert [email protected]'. > > This tests a :before_destroy callback which simply returns false to > prevent deletion. I verified that the callback is firing and haven't > been able to locate a difference between what's returned in the 3.0.4 > and 3.0.5 source code. A console session shows destroyed? returning > false as expected. > > Has this happened to anybody else? It's a simple test so I'd expect > others to have the same result if there's an actual problem. > Lighthouse shows a recent issue with before_destroy but it appears > unrelated.
Is this using a habtm association? There was a change to how destroy happens with those (which I personally think is broken) to do with when the before_destroy callbacks run relative to the clearing out of associated rows. It looks to me like a side effect of that change could be that the return value of destroy could change Fred -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
