[jira] [Resolved] (CALCITE-5044) JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field

["Julian Hyde (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-5044.
----------------------------------
    Fix Version/s: 1.31.0
       Resolution: Fixed

Fixed in [a6a1e2ce|https://github.com/apache/calcite/commit/a6a1e2cef332893fd90286098869c56529e052c3]; thanks for the PR, [~wojustme]!

> JDBC adapter generates integer literal in ORDER BY, which some dialects wrongly interpret as a reference to a field
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-5044
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5044
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Xurenhe
>            Assignee: Xurenhe
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.31.0
>
>         Attachments: image-2022-03-17-21-45-22-988.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When there is a Sort RelNode that references an integer literal, the JDBC adapter converts this to a SQL ORDER BY clause that contains an integer literal as a sort key. Some dialects (most dialects, in fact) wrongly interpret as a reference to a field.
> There is ambiguous in the rel-to-sql's converter when meeting `order by constant `.
> Here is an example:
> {code:java}
> @Test void testOderByConstant() {
>   final Function<RelBuilder, RelNode> relFn = b -> b
>       .scan("EMP")
>       .project(b.literal(1), b.field(1), b.field(2))
>       .sort(RelCollations.of(ImmutableList.of(
>           new RelFieldCollation(0), new RelFieldCollation(1))))
>       .project(b.field(2), b.field(1))
>       .build();
>   final String expected = "";
>   relFn(relFn).ok(expected);
> } {code}
> Return sql:
> {code:java}
> SELECT "JOB", "ENAME"
> FROM "scott"."EMP"
> ORDER BY 1, "ENAME" {code}
> But, `ORDER BY 1` may mean 'sort by the first column in the select list'  because of SqlConformance#isSortByOrdinal.
> I keep this the same semantics, by apply the rule of `CoreRules#SORT_REMOVE_CONSTANT_KEYS`
> Should the rel_to_sql's converter support it natively?
> *CODE:* https://github.com/wojustme/calcite/blob/6ad04e85875d9202e592a78cca8db807c5bde362/core/src/test/java/org/apache/calcite/rel/rel2sql/RelToSqlConverterTest.java#L1601



--
This message was sent by Atlassian Jira
(v8.20.1#820001)