Bug #28037 Falcon OR fails if index exists (2)
Submitted: 23 Apr 2007 19:39
Reporter: Hakan Küçükyılmaz Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[23 Apr 2007 19:39] Hakan Küçükyılmaz
Description:
  	 If I have a table with two indexed columns, with a few rows, then a search
"x IS NULL OR y IS NULL" fails to find a row where both x and y are NULL.

This is similar to Bug 154 "OR fails if index exists", which is closed.
The difference is that I have two separately-indexed columns.

How to repeat:
mysql> create table t (s2 int, s3 int, key (s2), key (s3)) engine = jstar;
Query OK, 0 rows affected (0.01 sec)

mysql> insert into t values (0,0),(1,1),(null,null);
Query OK, 3 rows affected (0.01 sec)
Records: 3 Duplicates: 0 Warnings: 0

mysql> select * from t where s2 is null or s3 is null;
Empty set (0.00 sec)
[23 Apr 2007 19:41] Hakan Küçükyılmaz
Test case is falcon_bug_28037.test.