You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Thomas Nielsen (JIRA)" <ji...@apache.org> on 2007/10/07 18:00:50 UTC
[jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window
function
[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532976 ]
Thomas Nielsen commented on DERBY-2998:
---------------------------------------
Just to rule it out I applied the patch for DERBY-1905 (optimizer subquery cost way too high), and it didn't make a difference.
So it's something I'm not doing that's not causing the optimizer to push the WHERE clause into the subquery to make it stop...
> 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: row_number_prototype-2b.diff, row_number_prototype-2b.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.