<?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: Downgrade MySQL 5 to MySQL 4.1 on cPanel dedicated server</title>
	<atom:link href="http://www.supportfacility.com/blog/mysql/downgrade-mysql-5-to-mysql-41-on-cpanel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supportfacility.com/blog/mysql/downgrade-mysql-5-to-mysql-41-on-cpanel/</link>
	<description>Your outsourcing partner!</description>
	<lastBuildDate>Thu, 17 Feb 2011 17:35:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dave</title>
		<link>http://www.supportfacility.com/blog/mysql/downgrade-mysql-5-to-mysql-41-on-cpanel/comment-page-1/#comment-590</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 21 Apr 2008 15:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://supportfacility.com/blog/?p=24#comment-590</guid>
		<description>A couple of notes:

1) It&#039;s much better to do a mysqldump of your databases than to do a file restore of the databases. This dump can be properly restored into MySQL 4 or 5 (depending on features used) rather than having to totally rebuild MySQL to accommodate the flat file restore.

http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html

2) MySQL 6.0 is in development with 5.1 in RC, 4.1 is likely going to be phased out very soon so rolling back is going to be a very short term solution. There&#039;s probably a better solution to the issue you are having than rolling back to 4.1</description>
		<content:encoded><![CDATA[<p>A couple of notes:</p>
<p>1) It&#8217;s much better to do a mysqldump of your databases than to do a file restore of the databases. This dump can be properly restored into MySQL 4 or 5 (depending on features used) rather than having to totally rebuild MySQL to accommodate the flat file restore.</p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html</a></p>
<p>2) MySQL 6.0 is in development with 5.1 in RC, 4.1 is likely going to be phased out very soon so rolling back is going to be a very short term solution. There&#8217;s probably a better solution to the issue you are having than rolling back to 4.1</p>
]]></content:encoded>
	</item>
</channel>
</rss>

