<?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, 23 May 2013 03:37:11 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Symfony Blog: Using Propel 1.4 detailed logging]]></title>
      <guid>http://www.phpdeveloper.org/news/13521</guid>
      <link>http://www.phpdeveloper.org/news/13521</link>
      <description><![CDATA[<p>
On the Symfony blog today there's <a href="http://www.symfony-project.org/blog/2009/11/08/using-propel-1-4-detailed-logging">a new post</a> by <i>Fabian Lange</i> about using the detailed logging ability of the <a href="http://propel.posterous.com/propel-140-stable-is-there">newly released version</a> of Propel (the database abstraction layer).
</p>
<blockquote>
Today <a href="http://propel.posterous.com/propel-140-stable-is-there">Propel 1.4 was released</a> and it contains some debugging goodies. We can use the DebugPDO class to get the nifty logging into the Web Debug Panel. However some more interesting information is turned off by default by Propel. 
</blockquote>
<p>
Features include time logging, memory logging and slow query logging - all that are simple to enable in your configuration under the details for your propel connection. You can see an example of the output from the logging <a href="http://www.symfony-project.org/uploads/assets/propel_web_debug_1_4.png">here</a>.
</p>]]></description>
      <pubDate>Thu, 12 Nov 2009 07:50:37 -0600</pubDate>
    </item>
  </channel>
</rss>
