[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-25 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959527#comment-16959527 ] benj commented on CALCITE-3402: --- [~danny0405], yes of course. Thx. > Allow RANGE with co

[jira] [Comment Edited] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-23 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957656#comment-16957656 ] benj edited comment on CALCITE-3402 at 10/23/19 3:26 PM: - >From

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-23 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957656#comment-16957656 ] benj commented on CALCITE-3402: --- Only try from Apache Drill (1.16 + latest master), the o

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-22 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956993#comment-16956993 ] benj commented on CALCITE-3402: --- I Just check MSSQL 2017 and Oracle 11 that work like Pos

[jira] [Comment Edited] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-22 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956811#comment-16956811 ] benj edited comment on CALCITE-3402 at 10/22/19 9:13 AM: - Your

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-22 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956811#comment-16956811 ] benj commented on CALCITE-3402: --- Your explanation make senses. I'm agree for the RANGE. B

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-18 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954457#comment-16954457 ] benj commented on CALCITE-3402: --- I think the RANGE with compound may be problematic when

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-18 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954409#comment-16954409 ] benj commented on CALCITE-3402: --- "SQL03 7.10 Rule 11a" is probably a reference of the SQL

[jira] [Comment Edited] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-18 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954354#comment-16954354 ] benj edited comment on CALCITE-3402 at 10/18/19 8:05 AM: - Yes o

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-18 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954354#comment-16954354 ] benj commented on CALCITE-3402: --- Yes of course, these 2 expressions are well equivalent

[jira] [Comment Edited] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-17 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952633#comment-16952633 ] benj edited comment on CALCITE-3402 at 10/17/19 12:47 PM: -- Wit

[jira] [Commented] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-16 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952633#comment-16952633 ] benj commented on CALCITE-3402: --- With Drill 1.16 and 1.17 (from 2019-10-14) ROWS is not e

[jira] [Updated] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-14 Thread benj (Jira)
[ https://issues.apache.org/jira/browse/CALCITE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] benj updated CALCITE-3402: -- Description: It will be very useful to have the capacity to use compound ORDER BY clause with RANGE {code:sq

[jira] [Created] (CALCITE-3402) Allow RANGE with compoud ORDER BY clause

2019-10-11 Thread benj (Jira)
benj created CALCITE-3402: - Summary: Allow RANGE with compoud ORDER BY clause Key: CALCITE-3402 URL: https://issues.apache.org/jira/browse/CALCITE-3402 Project: Calcite Issue Type: Improvement

[jira] [Created] (CALCITE-3244) Decorrelating sub-queries - Adding Implicit RowID support

2019-08-12 Thread benj (JIRA)
benj created CALCITE-3244: - Summary: Decorrelating sub-queries - Adding Implicit RowID support Key: CALCITE-3244 URL: https://issues.apache.org/jira/browse/CALCITE-3244 Project: Calcite Issue Type: I