db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-2526) Wrong query results due to column ordering in UNION view
Date Sat, 26 May 2007 02:20:16 GMT

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

Bryan Pendleton reassigned DERBY-2526:

    Assignee: A B  (was: Bryan Pendleton)

Army, thank you very much! Your description is very clear. It describes exactly the behavior
that I was seeing, and your analysis of the remapping feels spot-on. I agree with your fix,
and your patch fixes the problem in my environment, too.

Nothing like having another pair of eyes on things! Very good work.

I re-assigned the issue to you, assuming that you'll take it the rest of the way at this point.
Is that OK?

> Wrong query results due to column ordering in UNION view
> --------------------------------------------------------
>                 Key: DERBY-2526
>                 URL: https://issues.apache.org/jira/browse/DERBY-2526
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,,
>            Reporter: Bryan Pendleton
>         Assigned To: A B
>         Attachments: badQuery.log, d2526_v1.html, d2526_v1.patch, derby-2526.sql, DistinctTestNotes.txt,
firstTryPatch.diff, goodQuery.log
> I think both select statements in the attached repro script should return 1 row, but
in fact the first statement returns 1 row and the second returns zero rows.
> The only difference between the two statements is that the columns in the UNION view
are listed in a different order (bvw vs. bvw2).
> This seems like a bug to me; the order of the columns in the view definition shouldn't
matter, should it? 
> As Army noted on the derby-dev list, the fact that this reproduces with 10.0 means that
it is not caused by some of the 10.2 optimizer changes. Something else is going wrong.

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

View raw message