Frederick Cheung wrote: > You've got it out of find_by_sql so rails thinks its an existing row. > Furthermore rails doesn't think the object has changed since you > retrieved it from the database, so it shortcircuits the save (since > from its point of view there is nothing to save) > > Fred
Fred: Your explanation makes sense. If this is not a bug in ActiveRecord, then there IS a bug in the documentation -- it has to be one or the other. This is new territory for me: is there a writeup on how to properly report a documentation bug? A second (and lesser) question: is there a way to force a save? That would save me creating and copying a new one. Thanks. - ff -- Posted via http://www.ruby-forum.com/. -- 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.
