ActiveRecord
Posted: Wed Jan 11, 2006 4:26 pm
In the past few days I've been trying to figure out the latest hype over this ActiveRecord ORM approach (I blame it on Ruby on Rails!). It seems everyone and their dog is adding it to PHP Frameworks - even Zend apparently (though their use case seems to contravene the workings of PHP). What's confusing as hell however is the focus on metaprogramming - why do so many of these have "SHOW COLUMNS" sql calls (a mysql example) that must have occured to someone as a bit iffy performance wise? Is it necessary to automagically generate ActiveRecord subclasses at runtime? And why is so much functionality bundled into the parent class - and copied to evey inheriting object, rather than some abstracting all this repitition out to a referenced third object (saving on the memory it eats - which is important for many of us on shared hosts).
The more I look, the more I dislike, or itch to change. I even got confused after figuring out too late its not even the ActiveRecord design pattern Fowler describes!
Wondering if anyone here is using ActiveRecord (not the Fowler pattern - the Ruby On Rails misnamed one), and whether anyone has been convinced of its advantages (if any) over more traditional ORM methods...
The more I look, the more I dislike, or itch to change. I even got confused after figuring out too late its not even the ActiveRecord design pattern Fowler describes!
Wondering if anyone here is using ActiveRecord (not the Fowler pattern - the Ruby On Rails misnamed one), and whether anyone has been convinced of its advantages (if any) over more traditional ORM methods...