Incorrect handling of 'TRUE' in compound select

[monetdb-team]

Date: 2018-10-22 22:10:22 +0200
From: @mlkersten
To: SQL devs <>
Version: 11.29.3 (Mar2018)

Last updated: 2019-01-14 17:29:07 +0100

Comment 26649

Date: 2018-10-22 22:10:22 +0200
From: @mlkersten

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:62.0) Gecko/20100101 Firefox/62.0
Build Identifier:

The example below produces unexpected results depending on where the "true" occurs in the predicate. In particular, the second one produces the wrong result.

Reproducible: Always

Actual Results:

create table stmp(i integer); insert into stmp values(0), (1),(2);
select * from stmp S where S.i = 0;
select * from stmp S where true and S.i = 0;
select * from stmp S where S.i = 0 and true;

Comment 26654

Date: 2018-10-24 17:38:02 +0200
From: MonetDB Mercurial Repository <>

Changeset 225aedd6a7e7 made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=225aedd6a7e7

Changeset description:

Added test for bug #6654.

Comment 26655

Date: 2018-10-25 11:13:33 +0200
From: MonetDB Mercurial Repository <>

Changeset 92dfdd0da34a made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=92dfdd0da34a

Changeset description:

Fix for bug #6654 (i.e. don't stop predicate optimization early)