Ahh OK, useful to know. It would be helpful (in languages/frameworks in general) if a deprecation always had a comment on where to look for more information.
Generally Rails is good at this, but maybe that information isn't filtered through to APIDock.com. Cheers, Andy -- Andy Jeffries http://andyjeffries.co.uk/ #rubyonrails #mysql #jquery Registered address: 64 Sish Lane, Stevenage, Herts, SG1 3LS Company number: 5452840 On 9 April 2010 03:05, Joe Smith <[email protected]> wrote: > > :Frederick Cheung: > > Couldn't see any trace in the source of write attribute being marked >> as deprecated. >> > > It (ActiveRecord::Base#write_attribute) is not just deperecated, it is > gone. But another method with the same name in a different class > (ActiveRecord::AttributeMethods#write_attribute) replaced it. The new > function has the same functionality and is in scope virtually everywhere the > old one was. Thus to the end user, it is just the same as it has always > been. > > In other words the function moved. > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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.
