Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Keep in mind it's not deriving from a class, it's implementing an interface. In my mind that's a WORLD of difference. Also, Doctrine and Propel are obviously the the main choices in PHP and I dislike both of them (Although I haven't tried Doctrine 2, which is supposedly like Hibernate). They both violate the principles I outlined in my question. Commented Nov 18, 2011 at 20:28
  • After checking out Doctrine 2, it is very tightly coupled with the data objects. That's not really attractive either. Commented Nov 18, 2011 at 21:04
  • @LeviMorrison - isn't the repository pattern the best bet anyway? You define your entities, then you define repositories that know how to persist the entities, and inject those repositories into your business classes. If you want to change out your peristence logic, you change out your repository. The entities and business logic remain unaffected. Commented Nov 22, 2011 at 16:57