Re: Joining tables using IN (...) clause returns duplicate rows
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. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Joining tables using IN (...) clause returns duplicate rows
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 [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
