<?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>Mon, 20 May 2013 09:34:02 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Metapundit.net: Code Smells II]]></title>
      <guid>http://www.phpdeveloper.org/news/6582</guid>
      <link>http://www.phpdeveloper.org/news/6582</link>
      <description><![CDATA[<p>
Following up from the <a href="http://metapundit.net/sections/blog/code_smells_and_design_principles">previous article</a> on the Metapundit.net blog, there's <a href="http://metapundit.net/sections/blog/148">part two</a> of the "Code Smells" series - a look at bad things to do in your code (to make it "smell").
</p>
<blockquote>
This (and any subsequent posts in the series) will be more limited in scope - a single bad example and a corresponding solution.
</blockquote>
<p>
This time, <a href="http://metapundit.net/sections/blog/148">the spotlight</a> is on parameterised queries - inserting the variables directly into a SQL statement string versus filtering them or inserting them via a custom query() function. He points out that there's no need to create this kind of filtering/database handling class on your own, though - there's already been one created by the fine folks of PEAR (using the <a href="http://pear.php.net/manual/en/package.database.db.db-common.autoexecute.php">autoExecute function</a).
</p>]]></description>
      <pubDate>Thu, 26 Oct 2006 09:14:00 -0500</pubDate>
    </item>
  </channel>
</rss>
