Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <30476176.49231272425673041.JavaMail.jira@thor>
Date: Tue, 27 Apr 2010 23:34:33 -0400 (EDT)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4371) Non-selected columns for SELECT
 DISTINCT allowed in ORDER BY clause if ordered by expression
In-Reply-To: <809488972.1252323237535.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861661#action_12861661 ] 

Bryan Pendleton commented on DERBY-4371:
----------------------------------------

It sounds like your proposed patch would cause
a query which previously passed to get an error instead.

This is the sort of thing that we always think very carefully
about, because people may be currently using queries
like this, and depending on them, and so we are hesitant
to disrupt functionality that is currently operational for fear
of breaking existing applications.

In this particular case, we can see by using the Subversion "annotate" feature
http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/orderby.out?view=annotate
 that the particular query was changed by DERBY-2351 in revision 637529:
http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/orderby.out?r1=637528&r2=637529&

I think that the next step is probably to have a close review of the
DERBY-2351 notes and try to understand why the DERBY-2351 changes
are in conflict with the changes in your proposed patch.

It's quite possible that your patch is implementing the desired behavior,
but it would better still if we can understand why DERBY-2351 felt that
the other behavior was desirable.


> Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4371
>                 URL: https://issues.apache.org/jira/browse/DERBY-4371
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1
>            Reporter: Bernt M. Johnsen
>            Assignee: C.S. Nirmal J. Fernando
>            Priority: Critical
>         Attachments: DERBY-4371-2.diff, DERBY-4371.diff
>
>
> How to repeat:
> ij> create table t (i integer, j integer);;
> 0 rows inserted/updated/deleted
> ij> insert into t values (1,2),(1,3);
> 2 rows inserted/updated/deleted
> ij> select distinct i from t order by j;
> ERROR 42879: The ORDER BY clause may not contain column 'J', since the query specifies DISTINCT and that column does not appear in the query result.
> ij> select distinct i from t order by j*2;
> I          
> -----------
> 1          
> 1          
> 2 rows selected

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