db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3276) Order by on aggregate always does a sort even if the sort is not needed.
Date Mon, 17 Aug 2009 11:22:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-3276:
--------------------------------------

    Bug behavior facts:   (was: [Regression])

It looks like the regression box was checked in one of the big bulk updates in the recent
revamping of the bug database. I cannot find any traces of this bug being marked as a regression
before that change (searched the mail archives for notifications sent on creation/update of
this issue), so I'm unchecking the regression box. If this actually is a regression, please
update the issue and add a comment about which versions behave as expected, and which don't.

> Order by on aggregate always does a sort even if the sort is not needed.
> ------------------------------------------------------------------------
>
>                 Key: DERBY-3276
>                 URL: https://issues.apache.org/jira/browse/DERBY-3276
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Manish Khettry
>
> See DERBY-3231 for details.
> A few different variations of queries that do not need a sort are:
> select b, max(a) from yy where a=5 group by b order by max(a) asc;
> select b, max(a) from yy where a=5 group by b order by max(a) desc;
> Also consider
> select a, sum(b) from yy group by a having sum(b) = 2 order by sum(b);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message