<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tinsology &#187; Databases</title>
	<atom:link href="http://tinsology.net/category/databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://tinsology.net</link>
	<description>Read Me</description>
	<lastBuildDate>Wed, 10 Mar 2010 22:50:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Metadata</title>
		<link>http://tinsology.net/2009/07/metadata/</link>
		<comments>http://tinsology.net/2009/07/metadata/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 05:04:26 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[meta]]></category>
		<category><![CDATA[metadata]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=794</guid>
		<description><![CDATA[Throughout the life of a database there may come times when it needs to be updated to incorporate changes or new features. This may involve adding new attributes to existing entities; adding new columns to tables. The problem with this is that in a populated database, modifying the database schema can be very expensive with regard to performance. This is not something you want to do frequently on a live site. One method which not only makes your database more resilient to future change, but also improves modularity is the use of metadata. 
 
You don't have to look very <a href="http://tinsology.net/2009/07/metadata/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/pdo-use-it/' rel='bookmark' title='Permanent Link: PDO&#8230; Use It'>PDO&#8230; Use It</a></li>
<li><a href='http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/' rel='bookmark' title='Permanent Link: Creating a Secure Login System the Right Way'>Creating a Secure Login System the Right Way</a></li>
<li><a href='http://tinsology.net/2010/02/php-confirmation-emails/' rel='bookmark' title='Permanent Link: PHP Confirmation Emails'>PHP Confirmation Emails</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/07/metadata/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating a Secure Login System the Right Way</title>
		<link>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/</link>
		<comments>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/#comments</comments>
		<pubDate>Tue, 30 Jun 2009 06:03:13 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[hash]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[secure]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=663</guid>
		<description><![CDATA[Making a custom login system is a common task for beginning PHP developers. Jumping right into it, however, may not be the best approach. There are several important aspects do building a login system that not only makes it work, but makes it safe. <a href="http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/validating-user-input/' rel='bookmark' title='Permanent Link: Validating User Input'>Validating User Input</a></li>
<li><a href='http://tinsology.net/2010/02/php-confirmation-emails/' rel='bookmark' title='Permanent Link: PHP Confirmation Emails'>PHP Confirmation Emails</a></li>
<li><a href='http://tinsology.net/2009/07/metadata/' rel='bookmark' title='Permanent Link: Metadata'>Metadata</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>Validating User Input</title>
		<link>http://tinsology.net/2009/04/validating-user-input/</link>
		<comments>http://tinsology.net/2009/04/validating-user-input/#comments</comments>
		<pubDate>Thu, 09 Apr 2009 17:51:14 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Validation]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=370</guid>
		<description><![CDATA[Whenever you write an application that takes user input, you must assume users fall into two categories. Users who are incompetent, meaning that they are likely to provide incorrect input, and users that are attempting to exploit the system, meaning that they are trying to access, destroy, or manipulate information that they should not be able to. <a href="http://tinsology.net/2009/04/validating-user-input/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/01/intercepting-email-with-php/' rel='bookmark' title='Permanent Link: Intercepting Email with PHP'>Intercepting Email with PHP</a></li>
<li><a href='http://tinsology.net/2009/12/a-supplement/' rel='bookmark' title='Permanent Link: A Supplement'>A Supplement</a></li>
<li><a href='http://tinsology.net/2009/05/opera-tab-override-user-js/' rel='bookmark' title='Permanent Link: Opera Tab Override User JS'>Opera Tab Override User JS</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/validating-user-input/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PDO&#8230; Use It</title>
		<link>http://tinsology.net/2009/04/pdo-use-it/</link>
		<comments>http://tinsology.net/2009/04/pdo-use-it/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 03:17:25 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PDO]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=170</guid>
		<description><![CDATA[The majority of PHP code I see, whether it be posted by a beginner on a forum, or built into a large application, seems to suggest that the current standard when accessing a database is to make use of whatever database specific commands PHP provides for your particular database (ie mysql_query, mssql_query, etc). Often times, calls to these function are coupled with various attempts to prevent sql injections (such as calls to mysql_real_escape_string). Altogether, however, to me it seems clumsy and insecure. <a href="http://tinsology.net/2009/04/pdo-use-it/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/07/metadata/' rel='bookmark' title='Permanent Link: Metadata'>Metadata</a></li>
<li><a href='http://tinsology.net/2009/04/validating-user-input/' rel='bookmark' title='Permanent Link: Validating User Input'>Validating User Input</a></li>
<li><a href='http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/' rel='bookmark' title='Permanent Link: Creating a Secure Login System the Right Way'>Creating a Secure Login System the Right Way</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/pdo-use-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Database Analysis Through Simulation</title>
		<link>http://tinsology.net/2009/03/database-analysis-through-simulation/</link>
		<comments>http://tinsology.net/2009/03/database-analysis-through-simulation/#comments</comments>
		<pubDate>Tue, 10 Mar 2009 08:00:42 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Simulation]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=165</guid>
		<description><![CDATA[Making adjustments to a database schema after it has gone into use is a daunting task. Whether it be because of efficiency issues or the incorporation of a new feature, this is a situation you should avoid at all costs. Often times, however, mistakes and inefficiencies are difficult to spot at implementation time. Only when your database has become populated, often by users who are counting on your applications to be reliable, do these things come to light. So what can you do? One solution is to run a simulation. <a href="http://tinsology.net/2009/03/database-analysis-through-simulation/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/07/metadata/' rel='bookmark' title='Permanent Link: Metadata'>Metadata</a></li>
<li><a href='http://tinsology.net/2009/03/genetic-algorithm-problems/' rel='bookmark' title='Permanent Link: Genetic Algorithm Problems'>Genetic Algorithm Problems</a></li>
<li><a href='http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/' rel='bookmark' title='Permanent Link: Creating a Secure Login System the Right Way'>Creating a Secure Login System the Right Way</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/03/database-analysis-through-simulation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
