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] Updated: (DERBY-2526) Wrong query results due to column ordering in UNION view
Date Tue, 10 Apr 2007 14:31:32 GMT

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

Bryan Pendleton updated DERBY-2526:

    Attachment: firstTryPatch.diff

Moving the transitive closure processing earlier fixes this test case, so that
seems promising. I tried running the entire test suite and got about a
dozen test failures:
- lang/grantRevokeDDL.sql
- lang/outerjoin.sql
- lang/subqueryFlattening.sql
- lang/wisconsin.java
- lang/GroupByExpressionTest
- lang/DistinctTest
- derbynet/csPrepStmt.java
- derbynet/testconnection.java
- SecurityPolicyReloadingTest
- lang/UpdateCursorTest

I'm not sure that all of these are related to this change, but the "lang" suite
failures are definitely connected.

Still, the overall results seem promising, so I think I shall analyze the
test differences in more detail and try to understand how the change
provoked those failures.

I'll attach this first try patch to share the ideas. It is not for commit.

> 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: Bryan Pendleton
>         Attachments: badQuery.log, derby-2526.sql, 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