That’s just the tip of the iceberg.
The documentation states that ActiveResource behaves “very similarly to Active Record”. But ActiveResource doesn’t support any of the meta-data that ActiveRecord uses (like belongs_to, decease has_many, etc). So even the simplest cases behave radically different than you might expect.
A small sampling of things that don’t work:
a_person = Person.new a_person.name = “Luke“ #No method something= !! a_person.parent #No belongs_to a_person.children #No has_many
This is all fine if you are writing an app from scratch to use ActiveResource (well.. that’s debatable). At Medical Decision Logic, we needed to replace ActiveRecord with ActiveResource in an app with 50,000 lines of Ruby code. So we wrote Hyperactive Resource.
Hyperactive Resource extends ActiveResource::Base to make it.. work properly. You should use it. It’s awesome.
Check it out at http://github.com/lukegalea/hyperactiveresource/wikis