[
https://issues.apache.org/jira/browse/DERBY-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4331:
----------------------------------
my plan for this fix is going to be the proposed patch along with adding the
new test cases for 4331 to the test suite. I am running full set of tests
against trunk now and analysing the wisconsin diffs.
I've posted the wisconsin diffs which as is the case for query plan diffs are
quite extensive
(15k lines) - but so far nothing surprising.
If all goes well I would first check into trunk and then subsequently would
like to backport to 10.5 and then hopefully a new 10.5 apache release could be
made (along with whatever we are allowed to do to make it unlikely apache users
will use the previous one).
I plan on checking in even if there are a few cases where we use to do sort
avoidance and now
we don't. If I do this I would file a new JIRA issue outlining these cases,
which could be addressed
later. Note these would only represent performance enhancements, the queries
would be returning
correct results.
I would appreciate it if anyone thinks this is a bad idea to let me know sooner
than later.
> Join returns results in wrong order
> -----------------------------------
>
> Key: DERBY-4331
> URL: https://issues.apache.org/jira/browse/DERBY-4331
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.2.0, 10.6.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Mike Matrigali
> Attachments: createDBsimpler.txt, createDBsimplerVer2.txt,
> derby4331_do_not_commit.diff, notorderby4331.zip, orderby4331.zip, repro.sql,
> repro2.sql, repro2_qryplan.txt, wisconsin.diff
>
>
> In Derby 10.5.2.0, the query below started returning results in wrong order
> (note the ORDER BY clause). Derby 10.5.1.1 gives the expected ordering.
> ij> SELECT CS.ID
> FROM
> CHANGESETS CS, FILECHANGES FC, REPOSITORIES R, FILES F, AUTHORS A
> WHERE
> R.PATH = '/var/tmp/source5923202038296723704opengrok/mercurial' AND
> F.REPOSITORY = R.ID AND A.REPOSITORY = R.ID AND
> CS.REPOSITORY = R.ID AND CS.ID = FC.CHANGESET AND F.ID = FC.FILE AND
> A.ID = CS.AUTHOR AND
> EXISTS (
> SELECT 1
> FROM FILES F2
> WHERE
> F2.ID = FC.FILE AND F2.REPOSITORY = R.ID AND
> F2.PATH LIKE '/%' ESCAPE '#')
> ORDER BY CS.ID DESC;
> ID
> -----------
> 1
> 2
> 3
> 2
> 2
> 3
> 6 rows selected
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
