Re: Joining tables using "IN (...)" clause returns duplicate rows - Greg Bailey - com.mysql.lists.bugs

4 messages in com.mysql.lists.bugsRe: Joining tables using "IN (...)" c...

From	Sent On	Attachments
Greg Bailey	01 Feb 2002 13:16
Sinisa Milivojevic	02 Feb 2002 05:12
Greg Bailey	04 Feb 2002 12:12
Sasha Pachev	04 Feb 2002 15:38

Subject:	Re: Joining tables using "IN (...)" clause returns duplicate rows
From:	Greg Bailey (gbai...@i-link.net)
Date:	02/04/2002 12:12:17 PM
List:	com.mysql.lists.bugs

I guess I'm a little confused about the MySQL versions.

What is the real "production" version? If 4.0.2 can be called a production version, I'd gladly use it on my web site; however, it doesn't seem to indicate that on the MySQL home page. So if I find a bug in 3.23.47 that was fixed a "long time ago" as Mr. Milivojevic states, wouldn't I expect it to find its way into the 3.23.X series as the production series?

I really like MySQL and don't mean this as any type of a flame, just wondering what the versions mean. Thanks for any insight anyone can shed on this for me....

Greg Bailey

Sinisa Milivojevic wrote:

Greg Bailey writes:

Description:

Joining multiple tables together in a select statement with where clauses using the "IN (...)" construct generate duplicated output rows.

Hi!

I tested your case with 4.0.2 and got identical results from both queries.

This was some bug probably fixed long time ago.