<?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, 24 May 2012 15:00:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ulf Wendel's Blog: PHP mysqlnd query cache plugin quickstart is online!]]></title>
      <guid>http://www.phpdeveloper.org/news/17413</guid>
      <link>http://www.phpdeveloper.org/news/17413</link>
      <description><![CDATA[<p>
In a new post to his blog <i>Ulf Wendel</i> has pointed out that the <a href="http://blog.ulf-wendel.de/2012/php-mysqlnd-query-cache-plugin-quickstart-is-online/">mysqlnd query cache plugin quickstart is posted</a> on the <a href="http://docs.php.net/manual/en/mysqlnd-qc.quickstart.php">docs.php.net</a> site.
</p>
<blockquote>
New in the PHP manual: a <a href="http://docs.php.net/manual/en/mysqlnd-qc.quickstart.php">quickstart for the mysqlnd query cache plugin</a>. PECL/mysqlnd_qc, the mysqlnd query cache plugin, is transparent and ease to use. But, how? Some pointers have been given in assorted <A href="http://blog.ulf-wendel.de/2012/php-mysqlnd-query-cache-plugin-quickstart-is-online/www.slideshare.net/nixnutz/">presentations</a>, here on my blog and in some, few examples from the manual. Fixed. You can now browse a quickstart to gain a quick overview.
</blockquote>
<p>
The <a href="http://pecl.php.net/package/mysqlnd_qc">query cache plugin</a> can replace the query caching MySQL does and can help with things like multiple storage options (memory, APC, Memcache, etc) and almost no changes to your application. There's also a method (mysqlnd_qc_get_query_trace_log) that comes with the plugin that gives you a "stack trace" of every query run through the MySQL interface. 
</p>]]></description>
      <pubDate>Wed, 18 Jan 2012 12:12:21 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Fabien Potencier's Blog: PHP Serialization, Stack Traces, and Exceptions]]></title>
      <guid>http://www.phpdeveloper.org/news/11928</guid>
      <link>http://www.phpdeveloper.org/news/11928</link>
      <description><![CDATA[<p>
<i>Fabien Potencier</i> has <a href="http://fabien.potencier.org/article/9/php-serialization-stack-traces-and-exceptions">a new post</a> about a strange and hard to track down bug he was experiencing with serializing a <a href="http://symfony-project.org">symfony</a> form - it was throwing a <a href="http://us.php.net/pdo">PDO</a> exception.
</p>
<blockquote>
This exception is thrown by PDO because PDO instances are not serializable for good reasons. But it is weird because the sfForm class does not depend on PDO. How is it possible?
</blockquote>
<p>
After some poking around, he noticed that this was only an issue for those with sessions stored in the database (that's where the PDO comes in). The problem came with the validation error class - it extends the exception class and, because of how the error handling serializes the exception, it tries to serialize the PDO connection that's in the stack trace too.
</p>
<p>
His solution is to use a Serializable interface to define exactly what you want serialized and passed back out as the error to the rest of your script.
</p>]]></description>
      <pubDate>Wed, 11 Feb 2009 10:27:54 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Derick Rethan's Blog: XDebug 2 Released]]></title>
      <guid>http://www.phpdeveloper.org/news/8283</guid>
      <link>http://www.phpdeveloper.org/news/8283</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has <a href="http://derickrethans.nl/xdebug_2_released.php">officially announced</a> the release of XDebug 2 today on his blog:
</p>
<blockquote>
After almost four years of work, Xdebug 2 is finally ready. With improved functionality and many new features it is ready to totally change the way you develop in PHP. Some of the new features and updates include <a href="http://xdebug.org/docs/stack_trace">improved stack traces</a>, <a href="http://xdebug.org/docs/execution_trace">execution traces to files</a>, <a href="http://xdebug.org/docs/code_coverage">code coverage analysis</a> and much improved <a href="http://xdebug.org/docs/remote">remote debugging</a> support. Xdebug's <a href="http://xdebug.org/docs">documentation</a> has also been rewritten for more clarity.
</blockquote>
<p>
<i>Derick</i> also wants to find out who is user base is and has asked fellow developers and users to <a href="http://derickrethans.nl/who.php">send him a postcard</a> and let him know.
</p>
<p>
As always, you can get this latest version of the XDebug software from the project's website - <a href="http://xdebug.org/">XDebug.org</a>.
</p>]]></description>
      <pubDate>Wed, 18 Jul 2007 15:38:08 -0500</pubDate>
    </item>
  </channel>
</rss>

