<?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>Thu, 20 Jun 2013 00:15:22 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Anna Filina's Blog: Doctrine Translation in leftJoin()]]></title>
      <guid>http://www.phpdeveloper.org/news/14411</guid>
      <link>http://www.phpdeveloper.org/news/14411</link>
      <description><![CDATA[<p>
In a recent post to his blog <i>Anna Filina</i> looks at <a href="http://annafilina.com/blog/doctrine-translation-in-leftjoin/">internationalization in Doctrine</a> and how Symfony auto-builds things to take care of it for you.
</p>
<blockquote>
If you use Doctrine, then you probably know how lazy loading can hurt your performance. I carefully craft every query to everything that I need in one shot, but only what I need. One thing that evaded me at first was the i18n part. I am pleased with the way <a href="http://www.doctrine-project.org/">Doctrine</a> + <a href="http://www.symfony-project.org/">symfony</a> magically creates all my models and database tables with i18n support. 
</blockquote>
<p>
She talks a bit about the internationalization (i18n) support is put into the schema.yml file and the bit of confusion she had over how to handle a left join using its structure. The key lies in the Translation relationships.
</p>]]></description>
      <pubDate>Mon, 26 Apr 2010 11:39:33 -0500</pubDate>
    </item>
  </channel>
</rss>
