10 messages in com.mysql.lists.bugsRe: Repeatable bug in 3.23.29 - "WHER...
FromSent OnAttachments
Tobias Lind18 Dec 2000 12:55 
ctl...@apricot.com.hk18 Dec 2000 23:29 
Thimble Smith19 Dec 2000 01:03 
Thimble Smith19 Dec 2000 01:06 
Tobias Lind19 Dec 2000 03:59 
Thimble Smith19 Dec 2000 14:26 
ctl...@apricot.com.hk19 Dec 2000 20:13 
Michael Widenius20 Dec 2000 02:33 
Michael Widenius04 Jan 2001 14:54 
Tobias Lind05 Jan 2001 05:01 
Subject:Re: Repeatable bug in 3.23.29 - "WHERE expr IN (value,...)"
From:Thimble Smith (ti@mysql.com)
Date:12/19/2000 02:26:39 PM
List:com.mysql.lists.bugs

On Tue, Dec 19, 2000 at 12:59:57PM +0100, Tobias Lind wrote:

I have now uploaded a trace-file from mysqld 3.23.29 while running:

SELECT * FROM usrProfileTable2 WHERE usrName='toli'; (returns correct result - one row)

SELECT * FROM usrProfileTable2 WHERE usrName in ('toli'); (returns false result - empty set)

SELECT * FROM usrProfileTable2 WHERE usrName like 't%'; (returns false result - empty set)

Thanks for the trace file, Tobias. This one is odd, indeed. From the trace, it looks like a compiler bug - we just can't see how the index value is being changed from 0 to 16 inbetween the get_quick_select and the _mi_rkey. On my machine, this doesn't happen. Our trace files are identical until we enter _mi_rkey with inx set to 16.

Can you upgrade your compiler to gcc 2.95.2? Or, use one of our binaries?

Tim