[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959527#comment-16959527
]
benj commented on CALCITE-3402:
---
[~danny0405], yes of course. Thx.
> Allow RANGE with compoud ORDER BY
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959365#comment-16959365
]
Danny Chen commented on CALCITE-3402:
-
[~benj641], do you think we can close this issue now, it
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957656#comment-16957656
]
benj commented on CALCITE-3402:
---
Only try from Apache Drill (1.16 + latest master), the only working ROWS
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957245#comment-16957245
]
Julian Hyde commented on CALCITE-3402:
--
We probably already support ROWS with composite ORDER BY,
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956993#comment-16956993
]
benj commented on CALCITE-3402:
---
I Just check MSSQL 2017 and Oracle 11 that work like Postgres and
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956862#comment-16956862
]
Danny Chen commented on CALCITE-3402:
-
It's not surprise the cases you gave for RANGE and ROWS
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956811#comment-16956811
]
benj commented on CALCITE-3402:
---
Your explanation make senses. I'm agree for the RANGE.
But it's seem's
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956606#comment-16956606
]
Julian Hyde commented on CALCITE-3402:
--
Only allowing a single key makes a lot of sense.
If {{i}}
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954457#comment-16954457
]
benj commented on CALCITE-3402:
---
I think the RANGE with compound may be problematic when the "" is an
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954417#comment-16954417
]
Wang Yanlin commented on CALCITE-3402:
--
I think you are right about "SQL03 7.10 Rule 11a".
The
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954409#comment-16954409
]
benj commented on CALCITE-3402:
---
"SQL03 7.10 Rule 11a" is probably a reference of the SQL 2003 standard
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954386#comment-16954386
]
Wang Yanlin commented on CALCITE-3402:
--
Add this test case in *JdbcTest* to reproduce
{code:java}
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954354#comment-16954354
]
benj commented on CALCITE-3402:
---
Yes of course, these 2 expressions are well equivalent
* RANGE BETWEEN
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954089#comment-16954089
]
Julian Hyde commented on CALCITE-3402:
--
Maybe "{{RANGE BETWEEN unbounded PRECEDING AND unbounded
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952633#comment-16952633
]
benj commented on CALCITE-3402:
---
With Drill 1.16 and 1.17 (from 2019-10-14) ROWS is not either possible.
[
https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952372#comment-16952372
]
Julian Hyde commented on CALCITE-3402:
--
Did you try changing {{RANGE BETWEEN UNBOUNDED PRECEDING
16 matches
Mail list logo
