Complex expression with comparison evaluates incorrectly in WHERE clause #3854
Last updated: 2016-01-15 11:37:57 +0100
Date: 2015-11-09 11:26:50 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0
This bug is similar, but not the same as bug #3851. In the query below a comparison is used "15 > 1". The outcome of the comparison should not matter as the whole expression should evaluate to FALSE regardless, but the presence of the comparison makes it evaluate to TRUE. The bug does not seem to occur if anything else than a comparison with a variable is put here, including "15 > 1" or "TRUE".
This was tested in a version that already fixed bug #3851.
Steps to Reproduce:
Run the following commands in mclient:
CREATE TABLE test (id INTEGER, foo INTEGER);
This is a bug report from our client CHS.
Date: 2015-11-09 11:36:19 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a84afe3cb9fc
Date: 2015-11-09 13:47:14 +0100
fixed. The sql select push down lost one of the boolean expressions. This is fixed now..
Date: 2015-11-09 15:25:35 +0100
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3e237ae16358
The text was updated successfully, but these errors were encountered: