<?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 19:22:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[IBM developerWorks: Five common PHP database problems]]></title>
      <guid>http://www.phpdeveloper.org/news/5933</guid>
      <link>http://www.phpdeveloper.org/news/5933</link>
      <description><![CDATA[<p>
It seems like there's not a site out there anymore that doesn't use a database of some sort. Frankly, they're just a simple way to get the storage you need without the hassle of having to manage the resource yourself. It even comes with its own language to help query the data! Of course, with the good comes the bad, and <a href="http://www-128.ibm.com/developerworks/library/os-php-dbmistake/index.html">this new article</a> from IBM's developerWorks site about five common database mistakes.
</p>
<blockquote>
If only there were one way to use databases correctly... You can create database design, database access, and the PHP business logic code that sits on top of it in any number of ways, and you often end up getting it wrong. This article illustrates five common problems in database design, in the PHP code that accesses databases, and how to fix these problems when you see them.
</blockquote>
<p>
The problems <a href="http://www-128.ibm.com/developerworks/library/os-php-dbmistake/index.html">they discuss</a> are:
<ul>
<li>Using MySQL directly
<li>Not using auto-increment functionality
<li>Using multiple databases
<li>Not using relations
<li>The n+1 pattern
</ul>
Each of the items is discussed and explained with code samples for both the good and the bad side to make comparison easier. Knowing these issues before you develop your system definitely makes it easier, but they're still useful as a tool to fix things as well.
</p>]]></description>
      <pubDate>Wed, 02 Aug 2006 06:08:41 -0500</pubDate>
    </item>
  </channel>
</rss>
