[Rails] Re: Rails 2.3.2 bug? Detecting changed fields...

2009-03-31 Thread Meech
On further testing... x = MyModel.find(1) x.log << "append some text" >> x.changed => [] >> x.log => "old valueappend some text" The value is clearly changed in the resident copy of the model, yet it doesn't recognize it as changed. Meech wrote: > I have a text field in the database, lets

[Rails] Re: Rails 2.3.2 bug? Detecting changed fields...

2009-03-31 Thread Meech
Ah, I see. Too much work, doesn't feel like it's my job to tell what's changed or will change. I'll just switch to += Frederick Cheung wrote: > On Mar 31, 4:33 pm, Meech wrote: > > > Nothing is saved. > > > > If I do something like this: > > > > x = MyModel.find(1) > > x.log += "append so

[Rails] Re: Rails 2.3.2 bug? Detecting changed fields...

2009-03-31 Thread Frederick Cheung
On Mar 31, 4:33 pm, Meech wrote: > Nothing is saved. > > If I do something like this: > > x = MyModel.find(1) > x.log += "append some text" > x.save > > It works.   Seems like a bug. See http://ar.rubyonrails.org/classes/ActiveRecord/Dirty.html - if you change things inplace you need to use t