<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Optimize Wordpress Tables with Fix Database Plugin</title>
	<link>http://www.minger.net/2007/06/07/optimize-wordpress-tables-with-fix-database-plugin/</link>
	<description>The Long Tail of Web 2.0</description>
	<pubDate>Fri, 10 Oct 2008 23:24:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: The Happy Rock</title>
		<link>http://www.minger.net/2007/06/07/optimize-wordpress-tables-with-fix-database-plugin/#comment-47041</link>
		<dc:creator>The Happy Rock</dc:creator>
		<pubDate>Tue, 03 Jun 2008 17:47:05 +0000</pubDate>
		<guid>http://www.minger.net/2007/06/07/optimize-wordpress-tables-with-fix-database-plugin/#comment-47041</guid>
		<description>I just started getting the same error.  Thanks for posting the possible solution, I will look in to that plugin.</description>
		<content:encoded><![CDATA[<p>I just started getting the same error.  Thanks for posting the possible solution, I will look in to that plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress House Of Cards at Erik J. Heels</title>
		<link>http://www.minger.net/2007/06/07/optimize-wordpress-tables-with-fix-database-plugin/#comment-19285</link>
		<dc:creator>WordPress House Of Cards at Erik J. Heels</dc:creator>
		<pubDate>Thu, 28 Jun 2007 21:31:48 +0000</pubDate>
		<guid>http://www.minger.net/2007/06/07/optimize-wordpress-tables-with-fix-database-plugin/#comment-19285</guid>
		<description>[...] me. And on line 532 to boot! Some nerve. Googling that error message suggested that maybe my MySQL tables had become corrupted. The tables were probably boozing it up and watching too much [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] me. And on line 532 to boot! Some nerve. Googling that error message suggested that maybe my MySQL tables had become corrupted. The tables were probably boozing it up and watching too much [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
