title: Active Record Design Pattern?
body: <p>I've been looking into various ORM frameworks lately (mostly .net) and see that the Active Record design pattern is commonly used to persist data.</p>
  
  <p>I just wondered what everyone's take on the active record pattern is?  Personally I think it puts too much responsibility on the data object, be it just a data container or an entity bean.  I have always approached persisting objects from a central controller that exposes a method such as Persist() that takes in an interface say IEntityBean rather than letting the bean sort it's persistence out.  This is also the approach I take for population I get a dataset and generically populate the bean rather than letting the bean take in the dataset and populate itself.  I just don't like beans having logic.  Is this an old fashioned approach or do other share my fears?</p>
  
  <p>How do ORM frameworks that don't use the active record pattern mapping tables to object and object to tables?  Is a central controller that controls persisting a bad approach?</p>
  
  <p>Thanks for your opinions in advance!</p>