>>>>> "Anthony" == Anthony Louws <anthony.media@stripped> writes:
Anthony> Dear colleagues,
Anthony> I'm running MySql version 3.22.22. In a database I have the following
mysql> select distinct text from category c, category_text ct, text t
Anthony> where c.id = ct.categoryid and t.id = ct.textid;
Anthony> | text |
Anthony> | Reels |
Anthony> | Rods |
Anthony> | Seawater |
Anthony> | poor |
Anthony> | average |
Anthony> | best |
Anthony> | jet |
Anthony> | teun |
Anthony> 8 rows in set (0.00 sec)
Anthony> In the real situation I really need the distinct and I need some extra
Anthony> conditions on the category table, so that the reason for this join.
Anthony> The two queries should return the same resultset, but they don't!
Anthony> In your documentation I found no known bug or release note that this
Anthony> problem should be solved now in the latest version, but fortunately it
Anthony> is solved in 3.22.29! (thanx)
Anthony> I found a release note in 3.22.29 saying: "Fixed problem that could
Anthony> cause MySQL to touch freed memory when doing very complicated GROUP BY
Anthony> queries. ".
Anthony> Although there is no group by involved in my query I think that this is
Anthony> the fix I needed. (Is a distinct handled the same internally as a group
Anthony> by?) Anyway, the distinct problem is solved as well.
Anthony> May be you should mention this in your release notes for version
I found in the MySQL change log:
1999-07-29 Michael Widenius <monty@stripped>
* Fixed problem with DISTINCT on BLOB column
Somehow this didn't propagate to the changes section in the manual. Sorry