<?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>St. John Johnson &#187; MySQL</title>
	<atom:link href="http://www.stjohnjohnson.com/tag/mysql/feed" rel="self" type="application/rss+xml" />
	<link>http://www.stjohnjohnson.com</link>
	<description>This is a place for me to post my ideas, projects, tutorials, and resume for all to see</description>
	<lastBuildDate>Mon, 16 Jan 2012 05:14:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Storing Passwords in a Database</title>
		<link>http://www.stjohnjohnson.com/blog/storing-passwords-in-database</link>
		<comments>http://www.stjohnjohnson.com/blog/storing-passwords-in-database#comments</comments>
		<pubDate>Mon, 26 Apr 2010 15:48:00 +0000</pubDate>
		<dc:creator>St. John</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Best Practice]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[MD5]]></category>
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://www.stjohnjohnson.com/blog/storing-passwords-in-database</guid>
		<description><![CDATA[The other day, a friend of mine was asking for the best practice regarding stored passwords in a SQL database.&#160; His first idea was a simple hash (SHA1 in his case).&#160; While this is significantly better than plaintext and even MD5, it is still computationally feasible to reverse/guess the values if the server was compromised.&#160; [...]]]></description>
		<wfw:commentRss>http://www.stjohnjohnson.com/blog/storing-passwords-in-database/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Schema Diff Generator</title>
		<link>http://www.stjohnjohnson.com/blog/mysql-schema-diff-generator</link>
		<comments>http://www.stjohnjohnson.com/blog/mysql-schema-diff-generator#comments</comments>
		<pubDate>Tue, 22 Dec 2009 20:42:31 +0000</pubDate>
		<dc:creator>St. John</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.stjohnjohnson.com/blog/mysql-schema-diff-generator</guid>
		<description><![CDATA[At work, I occasionally need to move database changes from the development server to the live server.&#160; We have about a hundred tables, which makes it difficult to review by hand.&#160; So there is a comparison script that basically runs a `mysqladmin` schema dump on both databases and then diffs the two files.&#160; The result [...]]]></description>
		<wfw:commentRss>http://www.stjohnjohnson.com/blog/mysql-schema-diff-generator/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
