List:Bugs« Previous MessageNext Message »
From:Sasha Pachev Date:February 4 2002 11:38pm
Subject:Re: Joining tables using "IN (...)" clause returns duplicate rows
View as plain text  
On Monday 04 February 2002 01:12 pm, Greg Bailey wrote:
> 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?

Greg - you are absolutely right. Sinisa should have tested it on a 3.23 
version instead. 4.0.2 is not even out.

However, your test case worked as expected on 3.23.43-max, our binary. I 
noticed that your MySQL binary was from source using gcc 2.96, which is very 
likely the cause of the problem. I will add your test case to our gcc296 test 
in our test suite - hopefully it will help us find the bug and create a test 
case for RedHat. In the meantime, I strongly recommend that you switch to our 
binary.

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <sasha@stripped>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  
Thread
Joining tables using "IN (...)" clause returns duplicate rowsGreg Bailey1 Feb
  • Re: Joining tables using "IN (...)" clause returns duplicate rowsSinisa Milivojevic2 Feb
  • Re: Joining tables using "IN (...)" clause returns duplicate rowsGreg Bailey4 Feb
    • Re: Joining tables using "IN (...)" clause returns duplicate rowsSasha Pachev5 Feb