[MDEV-3083] LP:879864 - Wrong result with aggregate + two-column subselect Created: 2011-10-22  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Philip Stoev (Inactive) Assignee: Igor Babaev
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug879864.xml    

 Description   

This query:

SELECT MAX( f1 ) FROM t1 WHERE ( 5 , 9 ) IN ( SELECT 3 , 5 );

returns no rows even though it should return NULL (the where clause is false).

Repeatable in maria-5.3,maria-5.2,mysql-5.5

explain:

1 PRIMARY NULL NULL NULL NULL NULL NULL NULL NULL Select tables optimized away
2 DEPENDENT SUBQUERY NULL NULL NULL NULL NULL NULL NULL NULL No tables used

explain extended:

select max(`test`.`t1`.`f1`) AS `MAX( f1 )` from `test`.`t1` where <in_optimizer>((5,9),<exists>(select 3,5 having (((5 = 3) or isnull(3)) and ((9 = 5) or isnull(5)) and <is_not_null_test>(3) and <is_not_null_test>(5))))

test case:

CREATE TABLE t1 (f1 integer, key(f1)) engine=myisam;
insert into t1 values (1),(2);
SELECT MAX( f1 ) FROM t1 WHERE ( 5 , 9 ) IN ( SELECT 3 , 5 );



 Comments   
Comment by Igor Babaev [ 2011-12-27 ]

Re: Wrong result with aggregate + two-column subselect
This bug is fixed by the patch for bug #904345.

Comment by Elena Stepanova [ 2012-04-27 ]

Re: Wrong result with aggregate + two-column subselect
Fix for the bug #904345 was released in 5.2.11

Comment by Rasmus Johansson (Inactive) [ 2012-04-27 ]

Launchpad bug id: 879864

Generated at Thu Feb 08 06:46:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.