Wow, what a clusterf(#$. I am getting ready to write a new app in
3.x so I figured I would upgrade a legacy app to run on 1.9.x to ease
deployment, eliminate proxying requests, gain performance, etc, etc.
What a nightmare.
RubyGems 1.8 throws up all over the screen complaining about it's own
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.
M
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:
>
I have a text field in the database, lets call it log. If I do
something like this:
x = MyModel.find(1)
x.log << "append some text"
x.save
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.
--~--~-~--~--
4 matches
Mail list logo
