[ http://issues.apache.org/jira/browse/DERBY-466?page=all ] A B reopened DERBY-466: -----------------------
I would like to port this change to 10.1 and am currently working to do the merge and run the nightlies. If the tests pass tonight then I will post the merge command tomorrow. In the meantime, I am reopening the issue... > 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 > Attachments: 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
