[
https://issues.apache.org/jira/browse/DERBY-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-3002:
-----------------------------------
Attachment: setCurrentRow.diff
Attached patch calls setCurrentRow when returning a rolled-up grouped
result from the finishedResults lookaside buffer.
This patch is growing a bit long in the tooth. I'm considering the following
plan:
- moving the current patch toward commit
- filing followup issues for the remaining problems, namely:
- documentation is needed
- need to investigate the handling of the other varieties of ROLLUP which
are described by the SQL standard but not covered by this patch
- need to address the nullability-in-subqueries problem uncovered by Dag
Does this seem like a reasonable approach?
> Add support for GROUP BY ROLLUP
> -------------------------------
>
> Key: DERBY-3002
> URL: https://issues.apache.org/jira/browse/DERBY-3002
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.4.1.3
> Reporter: Bryan Pendleton
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: fixWhiteSpace.diff, IncludesASimpleTest.diff,
> passesRegressionTests.diff, prototypeChangeNoTests.diff,
> rewriteGroupByRS.diff, rollupNullability.diff, setCurrentRow.diff,
> UpdateToTrunkSep2009.diff, useAggregateObserver.diff, useLookahead.diff,
> withDagsCastTest.diff
>
>
> Provide an implementation of the ROLLUP form of multi-dimensional grouping
> according to the SQL standard.
> See http://wiki.apache.org/db-derby/OLAPRollupLists for some more detailed
> information about this aspect of the SQL standard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
