Details
Description
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.
Attachments
Attachments
Issue Links
- is part of
-
DERBY-2034 Tracking of bugs that lead to incorrect results being stored or returned to the client
- Closed
- is related to
-
DERBY-3023 Different result rows depending on the sequence of INNER JOIN and OUTER JOIN
- Closed
- relates to
-
DERBY-4679 Several left outer joins causes unstable query with incorrect results
- Closed
-
DERBY-5933 SQL sorting error
- Closed
-
DERBY-4695 Internal assignment of tablenumer, columnnumber looks wrong in query tree, although no ill effects are seen.
- Closed