[ http://issues.apache.org/jira/browse/DERBY-466?page=all ]
Andrew McIntyre closed DERBY-466:
---------------------------------
Resolution: Fixed
> Distinct in subselect can return wrong results
> ----------------------------------------------
>
> Key: DERBY-466
> URL: http://issues.apache.org/jira/browse/DERBY-466
> Project: Derby
> Type: Bug
> Components: SQL
> Environment: All Platforms
> Reporter: Manish Khettry
> Assignee: Manish Khettry
> Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.2
> Attachments: d466-10_1.patch, distinct.diff.txt
>
> The second query should return two rows but returns just one.
> ij> select * from t1;
> I |V
> ----------------------
> 1 |row 1
> 2 |row 2
> 2 rows selected
> ij> select * from t1, (select distinct 1 from t1) as sub(c);
> I |V |C
> ----------------------------------
> 1 |row 1 |1
> 1 row selected
> More specifically, this bug will show up when the sql layer does duplication
> elimination for distinct *without* a sorter (i.e. the underlying result set
> is already sorted). The result set will return correct data the first time,
> but after it is closed and re-opened it will not return any data rows.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
