<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 18 May 2013 09:10:12 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Francois Zeninotto's Blog: Comparing Propel, Doctrine and sfPropelFinder ]]></title>
      <guid>http://www.phpdeveloper.org/news/10568</guid>
      <link>http://www.phpdeveloper.org/news/10568</link>
      <description><![CDATA[<p>
<i>Francois Zeninotto</i> has <a href="http://redotheweb.com/2008/07/08/comparing-propel-doctrine-and-sfpropelfinder/">posted a comparison</a> of three different ORM (Object Relational Mapping) layers for PHP - Propel, Doctrine and sfPropelFinder (the last being a plugin of the <a href="http://www.symfony-project.org/">symfony</a> framework).
</p>
<blockquote>
When it comes to ORMs, it's all a matter of preference. Is it, really? This post compares side-by-side the code required to perform some simple operations with three OO database requesting API. The purpose is to demonstrate that productivity, and not only style, can vary a lot depending on the ORM you choose.
</blockquote>
<p>He's worked up a long list of examples including methods to:</p>
<ul>
<li>Retrieving an article by its primary key
<li>Retrieving the latest 5 articles
<li>Retrieving articles based on a complex AND/OR clause
<li>Retrieving articles authored by people of a certain group
<li>Retrieving an article and its category by the article primary key
<li>Retrieving articles and hydrating their author object and the author group
</ul>
<p>
Each one comes with their own (usually simple) code. His conclusions point out different "bests" of each - like sfPropelFinder being the "most magic" and that some of the limits of Propel are very frustrating.
</p>]]></description>
      <pubDate>Wed, 09 Jul 2008 10:24:59 -0500</pubDate>
    </item>
  </channel>
</rss>
