<?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>Tue, 21 May 2013 13:57:20 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Maggie Nelson's Blog: php|architect: Database Design for PHP Programmers by Mac Newbold]]></title>
      <guid>http://www.phpdeveloper.org/news/9721</guid>
      <link>http://www.phpdeveloper.org/news/9721</link>
      <description><![CDATA[<p>
<i>Maggie Nelson</i> has <a href="http://www.objectivelyoriented.com/2008/02/the_february_2008_issue_of_1.html">pointed out</a> an article in the most recently published edition of <a href="htt://www.phparch.com">php|architect</a> magazine (the February 2008 issue) that's an introduction to database design for programmers (by <i>Mac Newbold</i>).
</p>
<blockquote>
It's a pretty good article about database design and I think all PHP developers who are just starting to integrate databases in their applications should read it. However, there are a few things I'd like to add and point out.
</blockquote>
<p>
The "blurb" for the article mentions MySQL, PostgreSQL, Oracle, Microsoft SQL, SQLite and database schemas. You can find out more about this issue, including how to get your own copy, from the <a href="http://www.phparch.com/c/magazine/issue/67">php|architect website</a>.
</p>]]></description>
      <pubDate>Fri, 29 Feb 2008 07:53:00 -0600</pubDate>
    </item>
  </channel>
</rss>
