[
https://issues.apache.org/jira/browse/CALCITE-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745314#comment-17745314
]
Runkang He commented on CALCITE-5866:
-------------------------------------
If MSSQL (SQL Server) ignore the `ORDER BY` clause in a sub-query, we have two
options: make a new dialect-level setting, or just keep current, to let `ORDER
BY` ignored by MSSQL. But if there are some dialects throw exception in that
case, we may consider the first option.
Another thing is that, IMO the `ORDER BY` clause in a sub-query is useless,
because it not affects the final result. Please correct it if I am wrong.
> Not all dialects support sorting in sub-queries
> -----------------------------------------------
>
> Key: CALCITE-5866
> URL: https://issues.apache.org/jira/browse/CALCITE-5866
> Project: Calcite
> Issue Type: Bug
> Reporter: Will Noble
> Priority: Minor
>
> The rel-to-sql converter inserts subqueries in certain situations, such as
> when sorting by ordinal (see CALCITE-5768). Certain dialects, such as MSSQL
> (SQL Server) ignore the {{ORDER BY}} clause in a subquery. We may need a new
> dialect-level setting like {{canSortInSubQuery}} that dictates whether
> Calcite can safely insert sub-queries with {{ORDER BY}} clauses in them, or
> whether it must do everything in it's power to avoid that (such as refusing
> to sort by ordinal in cases where not all sort expressions are included in
> the {{SELECT}} list).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
