@DHH and Andrew : I agree with that - in a normal app development, you'll always want a model class and explicit associations - eventually.
Its probably a style preference for agile developers as to whether they are happy to immediately start work with derived associations (like the derived attr_accessors for fields in ARs now) instead of explicitly defining them. "Opinions" are great; so is choice. :)
Over time, we'll start to get feedback on people's development philosophies/strategies, for new Rails apps, Rails apps on legacy DBs, and non-Rails apps, etc.
@Rodrigo - Apparently post-Railsconf (read, post-Dave Thomas talk), some work was done on auto-validations by some people which is more magical that the simple validations that are available now; so I'll include those too; e.g. validates_uniqueness_of if its a sole-index, etc. Wonderful stuff!
Cheers
Nic
--
Dr Nic Williams
http://www.drnicwilliams.com - Ruby/Rails blog
skype: nicwilliams
(m) +31 62 494 8552
(p) +61 7 3102 3237 (finds me anywhere in the world)
(f) +61 7 3305 7572 (sends fax to my email)
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
