<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PHP + database + webserver</title>
	<atom:link href="http://behind.aotw.org/2006/10/12/phpdatabasewebserver/feed/" rel="self" type="application/rss+xml" />
	<link>http://behind.aotw.org/2006/10/12/phpdatabasewebserver/</link>
	<description>the backwash of a digital history project</description>
	<lastBuildDate>Sat, 13 Mar 2010 04:09:41 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doing Digitial History &#171; Bull Runnings</title>
		<link>http://behind.aotw.org/2006/10/12/phpdatabasewebserver/comment-page-1/#comment-2933</link>
		<dc:creator>Doing Digitial History &#171; Bull Runnings</dc:creator>
		<pubDate>Tue, 14 Nov 2006 18:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://behind.aotw.org/2006/10/12/phpdatabasewebserver/#comment-2933</guid>
		<description>[...] Part II [...]</description>
		<content:encoded><![CDATA[<p>[...] Part II [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Downey</title>
		<link>http://behind.aotw.org/2006/10/12/phpdatabasewebserver/comment-page-1/#comment-2612</link>
		<dc:creator>Brian Downey</dc:creator>
		<pubDate>Thu, 12 Oct 2006 21:12:39 +0000</pubDate>
		<guid isPermaLink="false">http://behind.aotw.org/2006/10/12/phpdatabasewebserver/#comment-2612</guid>
		<description>Hi Scott, thanks for coming by.

The AotW database contains just about everything displayed on the site, all the content. The text of all the articles, and resources like the Official Reports; pointers to, and properties of all images; information for military units, indivduals, weapons, tablets, maps, and casualties; bibliographic records; site change history and configuration. I rely on database id&#039;s (keys) to cross-reference and link officers to units to weapons to reports to stats to maps, etc.

The database also stores new submissions from members and unfinished work staged for publication, is the basis for the peer-review and approval scheme, and manages user accounts and security/session state.

Database design is very much an issue.  Not that mine is terribly well done! It would have been better if I had known what the database needed to do in its entirety before creating the first table, but the site didn&#039;t spring fully formed at the outset.  It&#039;s been evolutionary. I&#039;ve had to overhaul significantly at least twice in the past 3 years or so to include new requirements as we grew. I fully expect to have to do that again.

I use the term &lt;strong&gt;query&lt;/strong&gt;, by the way, to represent any transaction to/from the database. The example above--searching for an indivdual--is common, but queries are also used to read configuration data and customize site presentation, add users accounts, promote articles to &quot;production&quot;, and so forth.

I don&#039;t know what (if any) DB design tools are available specifically for mySQL, but I&#039;m sure the large user community would he helpful. You might start at &lt;a rel=&quot;nofollow&quot; href=&quot;http://www.mysql.org/&quot;&gt;http://www.mysql.org/&lt;/a&gt;  Given that mySQL is pretty much SQL-standard, and does most everything a high-end RDBMS can do, you may not need to limit yourself to mySQL products.

YMMV!

ps.  I know I put &quot;.html&quot; as a file type in the diagram above, but that might be misleading.  I just checked, and there&#039;s only one html file on the site (&lt;a title=&quot;AotW recruiting poster&quot; href=&quot;http://aotw.org/poster.html&quot;&gt;poster.html&lt;/a&gt;) - and that code&#039;s embarrassing.  Everything else is built on the fly from .php templates and includes, grabbing content from the database.  Some other file types are .xml  .js  .png  .gif   .ico  .css

This must be way too much information.</description>
		<content:encoded><![CDATA[<p>Hi Scott, thanks for coming by.</p>
<p>The AotW database contains just about everything displayed on the site, all the content. The text of all the articles, and resources like the Official Reports; pointers to, and properties of all images; information for military units, indivduals, weapons, tablets, maps, and casualties; bibliographic records; site change history and configuration. I rely on database id&#8217;s (keys) to cross-reference and link officers to units to weapons to reports to stats to maps, etc.</p>
<p>The database also stores new submissions from members and unfinished work staged for publication, is the basis for the peer-review and approval scheme, and manages user accounts and security/session state.</p>
<p>Database design is very much an issue.  Not that mine is terribly well done! It would have been better if I had known what the database needed to do in its entirety before creating the first table, but the site didn&#8217;t spring fully formed at the outset.  It&#8217;s been evolutionary. I&#8217;ve had to overhaul significantly at least twice in the past 3 years or so to include new requirements as we grew. I fully expect to have to do that again.</p>
<p>I use the term <strong>query</strong>, by the way, to represent any transaction to/from the database. The example above&#8211;searching for an indivdual&#8211;is common, but queries are also used to read configuration data and customize site presentation, add users accounts, promote articles to &#8220;production&#8221;, and so forth.</p>
<p>I don&#8217;t know what (if any) DB design tools are available specifically for mySQL, but I&#8217;m sure the large user community would he helpful. You might start at <a rel="nofollow" href="http://www.mysql.org/">http://www.mysql.org/</a>  Given that mySQL is pretty much SQL-standard, and does most everything a high-end RDBMS can do, you may not need to limit yourself to mySQL products.</p>
<p>YMMV!</p>
<p>ps.  I know I put &#8220;.html&#8221; as a file type in the diagram above, but that might be misleading.  I just checked, and there&#8217;s only one html file on the site (<a title="AotW recruiting poster" href="http://aotw.org/poster.html">poster.html</a>) &#8211; and that code&#8217;s embarrassing.  Everything else is built on the fly from .php templates and includes, grabbing content from the database.  Some other file types are .xml  .js  .png  .gif   .ico  .css</p>
<p>This must be way too much information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott smart</title>
		<link>http://behind.aotw.org/2006/10/12/phpdatabasewebserver/comment-page-1/#comment-2611</link>
		<dc:creator>scott smart</dc:creator>
		<pubDate>Thu, 12 Oct 2006 20:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://behind.aotw.org/2006/10/12/phpdatabasewebserver/#comment-2611</guid>
		<description>Thanls for documenting your site design.  I take it the database is used mainly for queries, so I assume that design was not that important an issue, but maybe I&#039;m wrong?  Does MySQL provide much in the way of DB design tools?</description>
		<content:encoded><![CDATA[<p>Thanls for documenting your site design.  I take it the database is used mainly for queries, so I assume that design was not that important an issue, but maybe I&#8217;m wrong?  Does MySQL provide much in the way of DB design tools?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
