[CALCITE-4507] 'a = 0 or a is null' should not be rewrite to a sarg 'a in (0, null)'

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.26.0
• Fix Version/s: 1.27.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Danny Chen
• Created: 22/Feb/21 09:51
• Updated: 18/Jun/21 08:43
• Resolved: 23/Feb/21 20:47

Description

SQL statements:

a = 0 or a is null -- returns true when a is null

a in (0, null) -- returns null when a is null

have different semantics when a is null, we should not represent it as a sarg after RexSimplify,

check this test in RexProgramTest:

@Test void testSimplifyInOr() {
        or(
            gt(vInt(), literal(0)),
            isNull(vInt())),
        ">(?0.int0, 0)");
  }

Issue Links

• duplicates: CALCITE-4446 Implement three-valued logic for SEARCH operator