[CALCITE-4590] Incorrect query result with fixed-length string

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.26.0
• Component/s: core
• Assignee: xiong duan
• Reporter: Roman Kondakov
• Created: 25/Apr/21 12:09
• Updated: 24/Nov/21 23:31

Description

Query may return wrong result when fixed-length strings (CHAR(N)) are used in OR/IN clause

@Test void test() {
    // Passed.
    CalciteAssert.that()
        .query("select * from (values (1, 'a'), (2, 'abc')) where EXPR$1 = 'a'")
        .returns("EXPR$0=1; EXPR$1=a  \n");

    // Failed. Only "EXPR$0=2; EXPR$1=abc\n" is returned
    CalciteAssert.that()
        .query("select * from (values (1, 'a'), (2, 'abc')) where EXPR$1 = 'a' or EXPR$1 = 'abc'")
        .returns("EXPR$0=1; EXPR$1=a  \n"
            + "EXPR$0=2; EXPR$1=abc\n");
  }

Issue Links

• is duplicated by: CALCITE-4647 INTERSECT returns wrong results
• is duplicated by: CALCITE-4648 Except returns wrong results
• is related to: CALCITE-4903 Avatica pads values returned from values-clause to same length
• is related to: CALCITE-4667 INNER join returns empty set
• is related to: CALCITE-4710 In the special scenario of the case when statement, the constant RexNode fails to be parsed.
• is related to: CALCITE-762 Trailing spaces on character literals
• is related to: CALCITE-1199 Incorrect trimming of CHAR when performing cast to VARCHAR
• is related to: CALCITE-2311 case when returns redundant white space
• is related to: CALCITE-4888 The type of generated search argument literal is wrong if the literal types of RelBuilder.in are different and compatible
• is related to: CALCITE-2321 The type of a union of CHAR columns of different lengths should be VARCHAR (based on a conformance setting)
• relates to: CALCITE-4493 Postgres/Mysql String Literal Equality Creates incorrect results.