Which design pattern do you prefer, Active Record or Repository?

When using Object Relational Mapping, you typically have two options, using the Active Record Pattern or using the Repository Pattern.

Active Record Pattern:

Entity e = Entity.create();
e.setSomeField("abc");
e.save();

Repository Pattern:

Entity e = Entity.create();
e.setSomeField("abc");
repository.save(e);

Both have their pros and cons - active record, you have fewer classes, but you mix your business logic into your data model, repository, you have a lot more classes, but your data model is separate from your business logic.

Which do you choose and why?

For some pointers, see:

• http://freephp.org/2016/03/the-repository-pattern-in-laravel-5/
• https://en.wikipedia.org/wiki/Active_record_pattern
• http://www.mehdi-khalili.com/orm-anti-patterns-part-1-active-record/
• http://www.primaryobjects.com/2010/03/17/using-the-nhibernate-repository-pattern-in-c-asp-net/