<?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"
	>
<channel>
	<title>Comments on: The wrong way to upgrade MySQL</title>
	<atom:link href="http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/</link>
	<description>You will probably want some waders, a pick axe, and one of those hats with a light on it before you go in here.</description>
	<pubDate>Tue, 06 Jan 2009 07:14:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Andrew</title>
		<link>http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2752</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 05 Jun 2006 18:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2752</guid>
		<description>so going from 4.0.17 to 4.1.x is as simple as copying my databases to the 4.1 data dir and starting 4.1?

i'm holding off on 5.0 due to that blog i read about all it's problems (memory leaks, procedure probs, performance, etc)</description>
		<content:encoded><![CDATA[<p>so going from 4.0.17 to 4.1.x is as simple as copying my databases to the 4.1 data dir and starting 4.1?</p>
<p>i&#8217;m holding off on 5.0 due to that blog i read about all it&#8217;s problems (memory leaks, procedure probs, performance, etc)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bergen</title>
		<link>http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2751</link>
		<dc:creator>Eric Bergen</dc:creator>
		<pubDate>Thu, 01 Jun 2006 06:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2751</guid>
		<description>The problem wasn't with mysql not upgrading the database it was with the user not reading anything before doing a major version upgrade. MySQL 5.0 can read tables from 4.1 just fine. The problem was purely application side.</description>
		<content:encoded><![CDATA[<p>The problem wasn&#8217;t with mysql not upgrading the database it was with the user not reading anything before doing a major version upgrade. MySQL 5.0 can read tables from 4.1 just fine. The problem was purely application side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2747</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 21 May 2006 16:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2747</guid>
		<description>I posted this before, but my comment was deleted.

An upgrade like this works fine with a database such as Sybase ASE - the database gets upgraded when the database server is restarted.

So it's definitely possible, and the user is right to expect it as a feature that should just work.

Hopefully MySQL will get this functionality in the future.</description>
		<content:encoded><![CDATA[<p>I posted this before, but my comment was deleted.</p>
<p>An upgrade like this works fine with a database such as Sybase ASE - the database gets upgraded when the database server is restarted.</p>
<p>So it&#8217;s definitely possible, and the user is right to expect it as a feature that should just work.</p>
<p>Hopefully MySQL will get this functionality in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: root</title>
		<link>http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2746</link>
		<dc:creator>root</dc:creator>
		<pubDate>Sat, 20 May 2006 10:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/2006/05/19/the-wrong-way-to-upgrade-mysql/#comment-2746</guid>
		<description>This works on Sybase ASE. It's a shame MySQL can't do it (yet).</description>
		<content:encoded><![CDATA[<p>This works on Sybase ASE. It&#8217;s a shame MySQL can&#8217;t do it (yet).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
