<?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 03:47:54 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Justin Carmony's Blog: PHP Design - Biggest Database Oversights]]></title>
      <guid>http://www.phpdeveloper.org/news/11461</guid>
      <link>http://www.phpdeveloper.org/news/11461</link>
      <description><![CDATA[<p>
<i>Justin Carmony</i> recently put together <a href="http://www.justincarmony.com/blog/2008/10/25/php-design-biggest-database-oversights/">a blog post</a> looking at the biggest database design oversights that PHP developers can make in their applications.
</p>
<blockquote>
I've thought of some of the biggest oversights I've had when working with PHP and MySQL and put them in a list. This is my personal list, and I'm sure some people can think of some other oversights that belong on the list as well. This list is just for PHP & MySQL, not PHP and any database. I know many people like using software like Doctrine to allow switching between different database types. That is beyond the scope of this article.
</blockquote>
<p>
He includes a list of five - not having a data access layer, designing for only one database connection, not including developer logging, having queries written in procedural code and no separation of reads and writes to the database.
</p>]]></description>
      <pubDate>Wed, 26 Nov 2008 14:14:56 -0600</pubDate>
    </item>
  </channel>
</rss>
