[
https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552346
]
Thomas Nielsen commented on DERBY-2998:
---------------------------------------
It seems we all agree on ROW_NUMBER() OVER () being compliant - good :)
The materialization path puts me in somewhat of a corner when I try to do
connect-the-dots. I get a two column ExecRow from the materialized resultset,
that is put into a three column ExecRow returned from
OLAPResultSet.getNextRowCore(). That results in an NPE at a later stage. I had
a look at HashJoins and ProjectRestrictNode which ought to do more or less the
same, as well as the javadocs for various descriptors available in
OLAPResultSet.getNextRowCore(), but it's not obvious (yet) how I'd go about
adding a column to the materialized ExecRow.
I hope to attach a doc patch later today.
> Add support for ROW_NUMBER() window function
> --------------------------------------------
>
> Key: DERBY-2998
> URL: https://issues.apache.org/jira/browse/DERBY-2998
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Thomas Nielsen
> Assignee: Thomas Nielsen
> Priority: Minor
> Attachments: d2998-4.diff, d2998-4.stat, d2998-5.diff, d2998-5.stat,
> d2998-6.diff, d2998-6.stat, d2998-7.diff, d2998-7.stat, d2998-test.diff,
> d2998-test.stat, d2998-test2.diff, d2998-test2.stat, d2998-test3.diff,
> d2998-test3.stat
>
>
> As part of implementing the overall OLAP Operations features of SQL
> (DERBY-581), implement the ROW_NUMBER() window function.
> More information about this feature is available at
> http://wiki.apache.org/db-derby/OLAPRowNumber
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
