<?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: About time</title>
	<atom:link href="http://www.denyerec.co.uk/about-time/feed" rel="self" type="application/rss+xml" />
	<link>http://www.denyerec.co.uk/about-time</link>
	<description>Photography, Graphic Design, Art, Code...</description>
	<lastBuildDate>Mon, 22 Jan 2018 15:17:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>By: Martiankeeper</title>
		<link>http://www.denyerec.co.uk/about-time/comment-page-1#comment-1914</link>
		<dc:creator><![CDATA[Martiankeeper]]></dc:creator>
		<pubDate>Fri, 26 Aug 2005 08:35:02 +0000</pubDate>
		<guid isPermaLink="false">/?p=205#comment-1914</guid>
		<description><![CDATA[I kind of assume that you are using some form of SQL based server (especially given the nasty &quot;SQL/DB Error&quot; messages popping up .. 
mySQL is it ???

I would suggest two databases .. for several reasons:

1) It is best to separate independently operating systems into their own environments. This make maintainability and portability easier.

2) If you ever want to shift &quot;just your gallery&quot; somewhere, you would have it (and associated data) in it&#039;s own database

3) Backup and restore procedures pose less risk as each database can be interrogated independently.

4) Security can be improved, with each database sporting it&#039;s own security settings and passwords.

(does this sound waffly enough yet??)

Apart from it looking good and trying to keep the coding simple, there are very few good reasons to keep everything in a single system (I&#039;m talking of course about small, single-server operations .. which I&#039;m assuming yours is?)

my &#163;0.02 worth ..

Martiankeeper]]></description>
		<content:encoded><![CDATA[<p>I kind of assume that you are using some form of SQL based server (especially given the nasty &#8220;SQL/DB Error&#8221; messages popping up ..<br />
mySQL is it ???</p>
<p>I would suggest two databases .. for several reasons:</p>
<p>1) It is best to separate independently operating systems into their own environments. This make maintainability and portability easier.</p>
<p>2) If you ever want to shift &#8220;just your gallery&#8221; somewhere, you would have it (and associated data) in it&#8217;s own database</p>
<p>3) Backup and restore procedures pose less risk as each database can be interrogated independently.</p>
<p>4) Security can be improved, with each database sporting it&#8217;s own security settings and passwords.</p>
<p>(does this sound waffly enough yet??)</p>
<p>Apart from it looking good and trying to keep the coding simple, there are very few good reasons to keep everything in a single system (I&#8217;m talking of course about small, single-server operations .. which I&#8217;m assuming yours is?)</p>
<p>my &#163;0.02 worth ..</p>
<p>Martiankeeper</p>
]]></content:encoded>
	</item>
</channel>
</rss>
