<?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: MySQL Bug?</title>
	<atom:link href="http://maisonbisson.com/blog/post/12158/mysql-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://maisonbisson.com/blog/post/12158/mysql-bug/</link>
	<description>A bunch of stuff I would have emailed you about.</description>
	<pubDate>Sat, 22 Nov 2008 15:47:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Raffaele</title>
		<link>http://maisonbisson.com/blog/post/12158/mysql-bug/#comment-235769</link>
		<dc:creator>Raffaele</dc:creator>
		<pubDate>Sun, 19 Oct 2008 20:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=12158#comment-235769</guid>
		<description>Hello!
True! I think that is a BUG.... and a BIG bug!
I have the same database in two machines: one is windows based with version 5.0.51b and it returns th BAD order, that is the ID order instead of date (in my case i had really the SAME problem as you... I need to group by due to the fact that in some cases I had joins taht multply the outputs)
With Mysql 5.0.37 in SlackwareLinux that (hopefully because is "on field" machine) 
Did you tried with newer verions (the last one is 5.0.64)?</description>
		<content:encoded><![CDATA[<p>Hello!<br />
True! I think that is a BUG&#8230;. and a BIG bug!<br />
I have the same database in two machines: one is windows based with version 5.0.51b and it returns th BAD order, that is the ID order instead of date (in my case i had really the SAME problem as you&#8230; I need to group by due to the fact that in some cases I had joins taht multply the outputs)<br />
With Mysql 5.0.37 in SlackwareLinux that (hopefully because is &#8220;on field&#8221; machine)<br />
Did you tried with newer verions (the last one is 5.0.64)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey Bisson</title>
		<link>http://maisonbisson.com/blog/post/12158/mysql-bug/#comment-195429</link>
		<dc:creator>Casey Bisson</dc:creator>
		<pubDate>Thu, 26 Jun 2008 03:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=12158#comment-195429</guid>
		<description>@Rob Wultsch: I think you found this post within minutes of when I published it. I edited it shortly after that to show the select on both ID and post_date_gmt, which isn't how the real query is written, but I did test it that way. The result of the first query, with or without post_date_gmt is the same: I get posts returned in ascending order of post ID.</description>
		<content:encoded><![CDATA[<p>@Rob Wultsch: I think you found this post within minutes of when I published it. I edited it shortly after that to show the select on both ID and post_date_gmt, which isn&#8217;t how the real query is written, but I did test it that way. The result of the first query, with or without post_date_gmt is the same: I get posts returned in ascending order of post ID.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Wultsch</title>
		<link>http://maisonbisson.com/blog/post/12158/mysql-bug/#comment-195269</link>
		<dc:creator>Rob Wultsch</dc:creator>
		<pubDate>Tue, 24 Jun 2008 19:43:02 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=12158#comment-195269</guid>
		<description>The group by in the first query is illegal on most databases.  When there is a select clause which specifies columns that are not in a group by clause, then the returned values of such columns are random randomly selected among available values. All sorts of undesirable behavior can happen due to misuse of a group by which is allowed in MySQL.  

My guess is that MySQL AB is not testing their builds against queries which should be illegal.</description>
		<content:encoded><![CDATA[<p>The group by in the first query is illegal on most databases.  When there is a select clause which specifies columns that are not in a group by clause, then the returned values of such columns are random randomly selected among available values. All sorts of undesirable behavior can happen due to misuse of a group by which is allowed in MySQL.  </p>
<p>My guess is that MySQL AB is not testing their builds against queries which should be illegal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>