<?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: Even minor upgrades are not always safe</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/</link>
	<description>Everything about MySQL Performance</description>
	<pubDate>Tue, 02 Dec 2008 14:08:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Dot Matrix &#187; Blog Archive &#187; The Big mySql Migration - the journey from 4.x to 5.x</title>
		<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2764</link>
		<dc:creator>Dot Matrix &#187; Blog Archive &#187; The Big mySql Migration - the journey from 4.x to 5.x</dc:creator>
		<pubDate>Mon, 25 Sep 2006 01:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2764</guid>
		<description>[...] I&#8217;ve found the MySql Performance blog (see this) to be very helpfull. My migration effort is still ongoing and I&#8217;m trying to make sure my rewritten queries work both on 4.x and 5.x, just in case things won&#8217;t work out and I&#8217;ll have to revert back to 4.x. Its not an easy going fun ride, but I guess it&#8217;s gotta happen. I hope I&#8217;ll have nothing more to tell and the rest of the work goes smoothly. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve found the MySql Performance blog (see this) to be very helpfull. My migration effort is still ongoing and I&#8217;m trying to make sure my rewritten queries work both on 4.x and 5.x, just in case things won&#8217;t work out and I&#8217;ll have to revert back to 4.x. Its not an easy going fun ride, but I guess it&#8217;s gotta happen. I hope I&#8217;ll have nothing more to tell and the rest of the work goes smoothly. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheeri</title>
		<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2290</link>
		<dc:creator>Sheeri</dc:creator>
		<pubDate>Wed, 06 Sep 2006 16:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2290</guid>
		<description>It's not about how much time you take -- it's about reading the release notes.

And I cannot believe someone didn't point out how awful comma joins are, and that &lt;a HREF="http://forum.mysqlperformanceblog.com/s/t/23/" rel="nofollow"&gt;the query&lt;/a&gt; should actually read:

SELECT c.*, rst.starttimename
FROM tblcourse c INNER JOIN tblcourse_category_extra ce USING (courseid)
LEFT JOIN tblref_starttime rst USING (starttimeid)
ORDER BY c.approveddate DESC

So much cleaner this way!</description>
		<content:encoded><![CDATA[<p>It&#8217;s not about how much time you take &#8212; it&#8217;s about reading the release notes.</p>
<p>And I cannot believe someone didn&#8217;t point out how awful comma joins are, and that <a href="http://forum.mysqlperformanceblog.com/s/t/23/" rel="nofollow">the query</a> should actually read:</p>
<p>SELECT c.*, rst.starttimename<br />
FROM tblcourse c INNER JOIN tblcourse_category_extra ce USING (courseid)<br />
LEFT JOIN tblref_starttime rst USING (starttimeid)<br />
ORDER BY c.approveddate DESC</p>
<p>So much cleaner this way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Chighizola</title>
		<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2261</link>
		<dc:creator>Sean Chighizola</dc:creator>
		<pubDate>Tue, 05 Sep 2006 19:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2261</guid>
		<description>The same thing happened to me with JOINS from 4.0 to 5.0 but I think it was a good thing to introduce standards.  I believe the more advanced users will understand the differences between releases and account for them to ensure a successful upgrade which is always time consuming and requires man hours for testing.  So upgrading should never be taken lightly.</description>
		<content:encoded><![CDATA[<p>The same thing happened to me with JOINS from 4.0 to 5.0 but I think it was a good thing to introduce standards.  I believe the more advanced users will understand the differences between releases and account for them to ensure a successful upgrade which is always time consuming and requires man hours for testing.  So upgrading should never be taken lightly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2248</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 05 Sep 2006 07:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2248</guid>
		<description>Well, 

As I understand this was done to make MySQL more standard in handling joins, this required new code which was found to have this problem.  It was however decided not to fix it as it break joins which were written not according to SQL standard. 

I think that was bad idea though. Large amount of MySQL users do not care about standard too much... just about their application working.</description>
		<content:encoded><![CDATA[<p>Well, </p>
<p>As I understand this was done to make MySQL more standard in handling joins, this required new code which was found to have this problem.  It was however decided not to fix it as it break joins which were written not according to SQL standard. </p>
<p>I think that was bad idea though. Large amount of MySQL users do not care about standard too much&#8230; just about their application working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Burton</title>
		<link>http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2241</link>
		<dc:creator>Kevin Burton</dc:creator>
		<pubDate>Tue, 05 Sep 2006 04:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/09/04/even-minor-upgrades-are-not-always-safe/#comment-2241</guid>
		<description>YEah..... joins broke for me too...... makes me mad :-/

Anyway... if all I have to do is wrap my from clause with parens then thats easy enough.......

Not sure why they decided to break ALL running mysql applications just for a couple parens.  Not a good idea guys.</description>
		<content:encoded><![CDATA[<p>YEah&#8230;.. joins broke for me too&#8230;&#8230; makes me mad :-/</p>
<p>Anyway&#8230; if all I have to do is wrap my from clause with parens then thats easy enough&#8230;&#8230;.</p>
<p>Not sure why they decided to break ALL running mysql applications just for a couple parens.  Not a good idea guys.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
